Fixed a Sticky Error After Schema Changes via the Connection Pooler
A schema change like adding a column, run through your PostgreSQL connection pooler, could leave it returning errors for up to an hour. That's fixed.
What's changed
- Managed PostgreSQL poolers now cap prepared statements at a safe limit on every instance
- Running DDL (like ALTER TABLE) through the pooler endpoint no longer risks a lingering error on your app's existing connections