PG Next DocsThis table reflects source checked on 22 October 2026. It is not production acceptance evidence or a service-level commitment.
| Capability | Scope and limitations |
|---|---|
| PostgreSQL versions | Compute source supports major versions 14–17. A newer PostgreSQL release does not establish PG Next support. |
| Regions | Choices are auto, germany and finland. Region IDs are not a promise about every data replica’s physical location. |
| Computes per branch | New source allows one compute per branch; it requires a separate migration/rollout, not verified live in this task. |
| Email registration | New source requires verification before account creation; depends on email configuration, registration settings and rollout. |
| MCP keys | Backend checks permissions/scope. Reading credentials is a separate permission; some operations require confirmation. |
| IP rules | Metadata only; not enforced on PostgreSQL connections by current compute runtime. |
| Restore | May require a compute restart; verify SQL data after restore. |
| Backup deletion | Removed metadata does not prove physical storage cleanup. |
| Data API, Data Masking, Integrations | Current pages state that these functions are unavailable; do not treat them as delivered features. |
| Autoscaling and pooler | Configuration fields do not establish complete runtime behavior. Verify your deployment before relying on them. |
| Pricing and payments | Follow current plan/checkout state. Docs do not establish new prices, refunds or an SLA. |
Before relying on a feature
Check the console and current resource state. HTTP 200, a build or an operation acknowledgment does not prove end-to-end success. For source changes not yet deployed, use the capabilities the operator has verified.