A dump/restore using pg_dumpall or use of pg_upgrade or logical replication is required for those wishing to migrate data from any previous release. See Section 18.6 for general information on migrating to new major releases.
Version 19 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:
Add server variable password_expiration_warning_threshold to warn about password expiration (Gilles Darold, Nathan Bossart) §
The default warning period is seven days.
Issue a warning after successful MD5 password authentication (Nathan Bossart) §
The warning can be disabled via server variable md5_password_warnings. MD5 passwords were marked as deprecated in PostgreSQL 18.
Remove RADIUS support (Thomas Munro) §
PostgreSQL only supported RADIUS over UDP, which is unfixably insecure.
Force standard_conforming_strings to always be on in the database server (Tom Lane) §
Dumps created using pre-PostgreSQL 19 versions of pg_dump or pg_dumpall, and using standard_conforming_strings = off, will not properly load into PostgreSQL 19 and later servers. Users should create dumps using PostgreSQL 19 or later versions of these applications, or use standard_conforming_strings = on.
Client applications still support operations with servers having standard_conforming_strings = off, for compatibility with old servers. The server variable escape_string_warning has been removed as unnecessary.
Disallow carriage returns and line feeds in database, role, and tablespace names (Mahendra Singh Thalor) §
pg_upgrade will also disallow upgrading of clusters that use such names. This was changed to avoid security problems.
Change the default index opclasses for inet and cidr data types from btree_gist to GiST (Tom Lane) § §
The btree_gist inet/cidr opclasses are broken because they can exclude rows that should be returned. pg_upgrade will disallow upgrading of clusters with btree_gist inet/cidr indexes.
Disallow system columns from being used in COPY FROM ... WHERE (Tom Lane) §
The values of such columns were not well-defined.
Change a json_array() call which returns no rows to return an empty JSON array (Richard Guo) §
This previously returned NULL.
Cause transactions to pass their READ ONLY and DEFERRABLE status to postgres_fdw sessions (Etsuro Fujita) §
This means READ ONLY transactions can no longer modify rows processed by postgres_fdw sessions.
Change default of max_locks_per_transaction from 64 to 128 (Heikki Linnakangas) §
Lock size allocation has changed, so effectively settings must now be doubled to match their capacity in previous releases.
Remove server variable io_workers (Thomas Munro) §
This has been replaced by four new variables; see Section E.1.3.1.2.
Change JIT to be disabled by default (Jelte Fennema-Nio) §
Previously JIT was enabled by default, and activated based on optimizer costs, but this costing has been determined to be unreliable. This change requires sites that are doing many large analytical queries to manually enable JIT.
Change parallel vacuum leaders and workers to share the cost-based vacuum delay limit (Bharath Rupireddy) §
Previously each worker process slept based only on the cost it incurred itself, so a parallel vacuum could consume several times the budget set by vacuum_cost_limit. With this change, VACUUM with parallel workers and cost-based delay enabled might run slower than in previous releases.
Rename column sync_error_count to sync_table_error_count in system view pg_stat_subscription_stats (Vignesh C) §
This is necessary since sequence errors are now tracked separately.
Rename wait event type BUFFERPIN to BUFFER and rename wait event BufferPin to BufferCleanup (Andres Freund) §
Remove wait event BufferContent and add more precise wait events BufferShared, BufferShareExclusive, and BufferExclusive (Andres Freund) §
Change index access method handlers to use a static IndexAmRoutines structure, rather than dynamically allocated ones (Matthias van de Meent) §
Remove optimizer hook get_relation_info_hook and add better-placed hook build_simple_rel_hook (Robert Haas) §
Change psql's \crosstabview command to honor the \pset null setting (Chao Li) §
Change full text search and pg_trgm to use the database's locale provider for character classification when parsing text (Jeff Davis) §
Previously, characters were classified using libc, regardless of the locale provider. In databases with a locale provider other than libc (e.g., ICU, builtin) and where the locale configured through that locale provider behaves differently from the LC_CTYPE setting configured for the database, particularly a LC_CTYPE of C, the output of some full text search and pg_trgm functions could change. When upgrading such databases using pg_upgrade, it is recommended to reindex all indexes which use full text search and pg_trgm after the upgrade, and to recompute any stored tsvector values.
Change how fuzzystrmatch functions handle non-ASCII characters (Peter Eisentraut, Jeff Davis) § §
dmetaphone() and dmetaphone_alt() now upper-case their input using the database's default collation rather than always using libc, and soundex(), metaphone(), and difference() now treat only ASCII letters as letters. When upgrading with pg_upgrade, it is recommended to reindex any indexes that use these functions after the upgrade.
Remove MULE_INTERNAL encoding (Thomas Munro) §
This encoding was complex and rarely used. Databases using it will need to be dumped and restored with a different encoding.