What enterprise teams should validate before production adoption
A new PostgreSQL release is an opportunity to reassess architecture, operations, and application requirements. It is not, by itself, a reason to upgrade. For enterprise teams, the decision should be based on measurable business benefit, workload compatibility, and the readiness of the operating model.
PostgreSQL 19 Strengthens the Enterprise Case
PostgreSQL has long offered enterprises a powerful open-source alternative to proprietary database platforms. Version 19 builds on that foundation with improvements in maintenance, performance, replication, application development, and security.
Notable capabilities include:
- REPACK introduces a native way to reorganize table contents and reclaim space. REPACK (CONCURRENTLY) is designed to perform the operation without blocking ordinary reads and writes. As with any table-rewrite operation, teams should still test resource consumption, disk headroom, runtime, and operational impact on representative data.
- The pg_plan_advice and pg_stash_advice extensions add options for influencing planner decisions and applying stored plan advice. They should be evaluated as extensions, with attention to supported query patterns, plan stability, permissions, and operational ownership.
- Parallel autovacuum can process table indexes using parallel workers. A scoring mechanism also helps determine which tables receive maintenance attention. These capabilities may improve maintenance throughput, but the outcome will depend on table size, workload pressure, I/O capacity, and configuration.
- Logical replication gains sequence synchronization capabilities. PostgreSQL 19 can also automatically enable logical replication when wal_level is set to replica, avoiding a restart in that specific configuration path. Teams should validate effective WAL settings, publication and subscription behavior, and sequence synchronization as part of migration testing.
- The new WAIT command allows a standby to wait until a specified LSN has been written, flushed, or replayed. This provides a building block for read-your-writes consistency when applications coordinate the LSN returned by a write with a subsequent read from a standby.
- Other changes include query-planner and execution improvements, faster foreign-key checks, asynchronous I/O enhancements, additional monitoring views, and updates to JSON and SQL functionality.
Together, these enhancements can improve maintainability, scalability, and developer productivity while addressing operational challenges in demanding production environments.
PostgreSQL 19 brings new capabilities for enterprise teams to evaluate as database architects continue to assess the role of PostgreSQL in their enterprise data platforms. Organizations are under increasing pressure to reduce database costs and proprietary-platform dependency while strengthening security, supporting emerging workloads, including agentic AI applications, and preserving deployment flexibility. With standard PostgreSQL, customers can choose where it runs: their cloud of choice, a region that meets data residency and compliance needs, or their own data center.
PostgreSQL 19 Release Status and Upgrade Planning
The PostgreSQL Global Development Group released PostgreSQL 19 Release Candidate 2 (RC 2) on November 12, 2026. The project announced November 19, 2026, as its target for general availability, pending any issues that could delay the final release. Use RC 2 to evaluate and test PostgreSQL 19 ahead of production adoption.
Database architects and platform teams can begin validating PostgreSQL 19 against representative workloads and non-functional requirements. This includes performance, extension and driver compatibility, security controls, backup and recovery, high availability, disaster recovery, observability, and automation. Production adoption should follow evidence from testing, not the calendar.
Spinnaker’s Recommendation
Use release candidates for evaluation, not production deployment. They provide an opportunity to determine whether PostgreSQL 19 fits an organization’s applications and operating model.
Before production adoption, Spinnaker recommends evaluating PostgreSQL 19 across five dimensions:
- Workload compatibility: Validate application behavior, SQL semantics, drivers, extensions, stored procedures, backup utilities, monitoring agents, connection poolers, and high-availability components.
- Performance: Benchmark representative production workloads rather than relying on generalized performance claims. Focus on execution plan changes, vacuum behavior, concurrency, replication lag, storage consumption, and recovery performance.
- Operational resilience: Test backup and recovery, failover, disaster recovery, point-in-time recovery, replication, patching, observability, and rollback procedures.
- Security and compliance: Review authentication, authorization, TLS configuration, logging, encryption, network controls, extension permissions, operating system hardening, vulnerability exposure, and compliance requirements.
- Lifecycle readiness: Confirm that required extensions and operational tools support version 19 before setting a production adoption date.
Treat November 19 as a release milestone, not a universal migration deadline. Evaluation can begin now. Production adoption should follow demonstrated readiness.
Plan for Compatibility Changes
A major-version upgrade requires more than checking whether an application starts. PostgreSQL 19 includes compatibility changes that should be assessed explicitly. Among the items called out in the official migration notes are:
- JIT is disabled by default. Workloads that rely on JIT for large analytical queries should be benchmarked, and JIT should be enabled deliberately where it provides a measurable benefit.
- standard_conforming_strings is always on at the server. Review legacy SQL and dump/restore workflows that depended on it being off; use PostgreSQL 19-compatible dump tooling and validate string-literal behavior.
- RADIUS authentication support has been removed. Environments using RADIUS must plan and test an alternative authentication method before upgrading.
- MD5 password authentication produces a warning. Treat this as a prompt to plan migration to SCRAM-SHA-256 rather than as a reason to defer indefinitely.
- The default max_locks_per_transaction has changed from 64 to 128, and the underlying lock-size allocation has changed. Review workloads with large numbers of locked relations and compare effective capacity rather than relying only on the numeric default.
- The io_workers setting has been removed and replaced by io_min_workers, io_max_workers, io_worker_idle_timeout, and io_worker_launch_interval. Review configuration management and tuning procedures.
- Full-text search and pg_trgm now use the database locale provider for character classification. Depending on locale configuration, indexes may need to be rebuilt and stored tsvector values recomputed after an upgrade. Review fuzzystrmatch behavior changes and reindex affected indexes where required.
- postgres_fdw now propagates READ ONLY and DEFERRABLE transaction characteristics to remote sessions. Applications that previously modified remote rows through a READ ONLY transaction must be reviewed.
This list is not a substitute for the complete PostgreSQL 19 migration notes. Upgrade planning should include a line-by-line review of the official notes, extension release information, and the organization’s own application and infrastructure dependencies.
PostgreSQL 19 Creates New Opportunities for Oracle Customers
For organizations with large Oracle estates, PostgreSQL 19 may strengthen the case for selective modernization. But moving from Oracle to PostgreSQL is a platform migration, not a database version upgrade.
Oracle environments often contain years of embedded business logic in PL/SQL packages, triggers, proprietary data types, database links, scheduler jobs, optimizer hints, security policies, and operational procedures. Some workloads are strong candidates for PostgreSQL. Others may require remediation or redesign or may be better suited to continued operation on Oracle.
For that reason, Spinnaker advocates a workload-by-workload approach.
Spinnaker can support the Oracle environment an organization relies on today while helping identify which workloads should remain, which need optimization, and which are suitable for PostgreSQL. This approach gives customers the time and evidence to make informed decisions without a premature platform change.
Spinnaker’s Assessment and Migration Services for PostgreSQL, powered by HexaCluster, support this process through:
- Oracle dependency and workload analysis
- Schema and code assessment
- Automated conversion assistance where appropriate
- Data movement and validation
- Change data capture
- Production readiness testing
- Controlled cutover planning
- Rollback preparation
Expertise in both Oracle and PostgreSQL matters because migration risks often arise from differences between the platforms. A migration partner must understand what the existing Oracle implementation does, why it was designed that way, and which behaviors must be preserved or deliberately changed.
With Oracle support in place during the transition, customers can modernize at a pace guided by their business needs rather than an arbitrary vendor deadline.
Security Must Be Part of the Architecture
PostgreSQL has a strong security foundation, but neither open-source licensing nor a recent release guarantees secure deployment. Security depends on sound architecture, careful configuration, disciplined maintenance, and responsive operational support.
PostgreSQL 19 also introduces a few security-related changes that are worth noting. It adds server-side support for TLS Server Name Indication (SNI), allowing a single PostgreSQL instance to present different certificates depending on the hostname used by the client. Hostname-to-certificate and key mappings are configured through the new PGDATA/pg_hosts.conf file.
The release also adds password-expiration warnings through the password_expiration_warning_threshold parameter, which defaults to seven days. In addition, PostgreSQL now issues a warning when a connection successfully authenticates using an MD5-encrypted password. This warning can be controlled through the md5_password_warnings parameter.
The MD5 warning is particularly useful for administrators reviewing older authentication configurations. MD5 password authentication was deprecated in PostgreSQL 18 and is planned for removal in a future release. Organizations should therefore review existing MD5 usage and plan a transition to SCRAM-SHA-256. These changes provide useful signals for improving certificate management and password security, although they should be considered part of a wider database security review rather than a replacement for established security controls.
Spinnaker’s security approach extends beyond applying patches. It includes:
- Vulnerability assessment and exposure analysis
- Configuration and architecture reviews
- Database and operating system hardening guidance
- Authentication and authorization reviews
- TLS and certificate management guidance
- Logging and audit readiness recommendations
- Analysis of extensions and software dependencies
- Risk-based remediation planning
- Compensating controls when immediate patching is impractical
- Security guidance for Oracle and PostgreSQL environments during coexistence and migration
These safeguards are especially important during an Oracle-to-PostgreSQL transition, which can change identity models, privilege structures, encryption controls, audit mechanisms, network paths, operational ownership, and recovery processes. Map and validate security requirements for the target environment rather than assuming they transfer automatically.
Choice Without a New Form of Lock-In
Beyond technical readiness, enterprises should consider long-term control and portability. Spinnaker sees these as central to PostgreSQL’s strategic value. That value can erode if an organization replaces its Oracle dependency with a proprietary PostgreSQL fork, a closed compatibility layer, or a platform-specific operating model that is difficult to leave.
Spinnaker’s strategy centers on standard PostgreSQL and vetted open-source components, with the aim of delivering enterprise-grade reliability and accountability while preserving architectural control and long-term portability. PostgreSQL 19 should reinforce customer choice, not narrow it.
What Enterprises Should Do Now
To put these principles into practice, organizations can use the release candidate period to:
- Inventory the PostgreSQL estate, extensions, and dependencies.
- Identify applications that could benefit from PostgreSQL 19.
- Establish performance and reliability baselines.
- Build representative test environments.
- Test upgrades, backups, restores, failovers, and rollbacks.
- Review security and compliance requirements.
- Assess Oracle workloads that may be candidates for PostgreSQL.
- Define production adoption criteria and decision gates.
For many enterprises, this preparation will lead to a phased strategy: maintain critical Oracle systems, migrate suitable workloads to PostgreSQL, and adopt version 19 once compatibility, security, and operational readiness have been demonstrated.
The Spinnaker View
PostgreSQL 19 is a promising step forward for enterprise adoption. Spinnaker welcomes the improvements and encourages organizations to evaluate them now, with a clear distinction between testing a release and committing to production.
Responsible modernization requires evidence, disciplined testing, security expertise, and operational accountability. It also requires a clear understanding of both the platform being adopted and the one being replaced.
Spinnaker can support that journey by protecting and optimizing existing Oracle estates, assessing and migrating suitable workloads, and providing ongoing enterprise support and security guidance for PostgreSQL.
The goal is not simply to deploy PostgreSQL 19. It is to help enterprises adopt PostgreSQL on their own terms, with clearer risk management, greater control, and no new form of lock-in.
Ready to evaluate PostgreSQL 19 or explore an Oracle-to-PostgreSQL migration?
Spinnaker Support can help build a workload-based roadmap, validate production readiness, and support both platforms throughout the transition.
Sources
PostgreSQL 19 RC 1 release announcement
PostgreSQL 19 RC 2 release announcement
PostgreSQL 19 Beta 1 announcement
Spinnaker Support PostgreSQL services
https://www.postgresql.org/about/news/postgresql-187-1712-1616-1520-1425-and-19-rc-2-released-3442/