Jump to:
Prevent trusted PL/Perl code from changing environment variables (Andrew Dunstan, Noah Misch) § § §
The ability to manipulate process environment variables such as PATH gives an attacker opportunities to execute arbitrary code. Therefore, “trusted” PLs must not offer the ability to do that. To fix plperl, replace %ENV with a tied hash that rejects any modification attempt with a warning. Untrusted plperlu retains the ability to change the environment.
The PostgreSQL Project thanks Coby Abrams for reporting this problem. (CVE-2024-10979)
Harden selectivity estimators against being attached to operators that accept unexpected data types (Tom Lane) § §
contrib/intarray contained a selectivity estimation function that could be abused for arbitrary code execution, because it did not check that its input was of the expected data type. Third-party extensions should check for similar hazards and add defenses using the technique intarray now uses. Since such extension fixes will take time, we now require superuser privilege to attach a non-built-in selectivity estimator to an operator.
The PostgreSQL Project thanks Daniel Firer, as part of zeroday.cloud, for reporting this problem. (CVE-2026-2004)
Harden contrib/pg_trgm against changes in string lowercasing behavior (Heikki Linnakangas) § §
Fix potential buffer overruns arising from the fact that in some locales lower-casing a string can produce more characters (not bytes) than were in the original. That behavior is new in version 18, and so is the bug.
The PostgreSQL Project thanks Heikki Linnakangas for reporting this problem. (CVE-2026-2007)
Fix oversight in the fix for CVE-2026-2007 (Zsolt Parragi) §
If the “bounds” array needed to be expanded, because the input contained more trigrams than the initial guess, generate_trgm_only didn't return the modified array pointer to its caller. That would lead to incorrect output from strict_word_similarity() and related functions, or in rare cases a crash. The faulty code is reached if the input string becomes longer when it's converted to lower case. The only known instances of that occur when an ICU locale is used with certain single-byte encodings.
Prevent unbounded recursion while processing startup packets (Michael Paquier) §
A malicious client could crash the connected backend by alternating rejected SSL and GSS encryption requests indefinitely.
The PostgreSQL Project thanks Calif.io (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-6479)
Fix assorted integer overflows in memory-allocation calculations (Tom Lane, Nathan Bossart, Heikki Linnakangas) § § § § § § § § §
Various places were incautious about the possibility of integer overflow in calculations of how much memory to allocate. Overflow would lead to allocating a too-small buffer which the caller would then write past the end of. This would at least trigger server crashes, and probably could be exploited for arbitrary code execution. In many but by no means all cases, the hazard exists only in 32-bit builds.
The PostgreSQL Project thanks Xint Code, Bruce Dang, Sven Klemm, and Pavel Kohout for reporting these problems. (CVE-2026-6473)
Properly quote subscription names in pg_createsubscriber (Nathan Bossart) §
The given subscription name was inserted into SQL commands without quoting, so that SQL injection could be achieved in the (perhaps unlikely) case that the subscription name comes from an untrusted source.
The PostgreSQL Project thanks Yu Kunpeng for reporting this problem. (CVE-2026-6476)
Detect faulty input when restoring attribute MCV statistics (Michael Paquier) §
The statistics restore functions were insufficiently careful about validating most-common-value statistics, and would accept values that could crash the planner later on.
The PostgreSQL Project thanks Jeroen Gui for reporting this problem. (CVE-2026-6575)
Use timing-safe string comparisons in authentication code (Michael Paquier) §
Use timingsafe_bcmp() instead of memcpy() or strcmp() when checking passwords, hashes, etc. It is not known whether the data dependency of those functions is usefully exploitable in any of these places, but in the interests of safety, replace them.
The PostgreSQL Project thanks Joe Conway for reporting this problem. (CVE-2026-6478)
Restrict logical decoding output plugins to the set specified by a new server parameter output_plugin_libraries (Jacob Champion) § §
Previously, a replication user could select any loadable library for logical decoding, allowing exploits of various sorts. To allow locking this down without breaking setups that worked before, introduce a whitelist of allowed output plugins.
By default, only the output plugins shipped as part of PostgreSQL (pgoutput and test_decoding) are included in output_plugin_libraries. Installations that rely on other output plugins must add them after updating the server, for example
output_plugin_libraries = 'pgoutput, test_decoding, my_trusted_decoder'
Additionally, pg_upgrade --check will fail if the output_plugin_libraries parameter on the new cluster does not permit the plugins of logical replication slots on the old cluster, when migrating from versions 17 and later. Make necessary additions to the new cluster's setting before performing pg_upgrade.
The PostgreSQL Project thanks Vladimir Tokarev and Yu Kunpeng for reporting this problem. (CVE-2026-6471)
Fix contrib/pgcrypto's PGP encryption to detect unsupported ciphers (Daniel Gustafsson) § §
Previously, if OpenSSL rejected the requested cipher (for example, because it is running in FIPS mode, or the legacy provider hasn't been loaded), pgcrypto failed to notice the failure and simply XOR'd the non-encrypted block with the plaintext, rendering the “encryption” trivially breakable. This will typically occur with deprecated or non-FIPS cipher algorithms (cipher-algo=blowfish/bf, twofish, cast5, or 3des).
By default, pgcrypto will now fail to decrypt any messages that were affected in this way. To allow retrieval of such data, a new option ignore-cipher-failure has been added to pgp_pub_decrypt() and pgp_sym_decrypt(). Setting ignore-cipher-failure=1 will restore their previous behavior, allowing the faulty encryption wrapper to be stripped off:
pgp_sym_decrypt(encrypted_column, any key, 'ignore-cipher-failure=1')
Once the affected messages are identified and stripped of their wrappers, they can then be re-encrypted with a modern algorithm. It is important however that the behavior of OpenSSL be the same as it was when the faulty messages were created: if the set of unsupported algorithms is not the same, this approach will not work. See the documentation for ignore-cipher-failure.
The PostgreSQL Project thanks Shishir Sharma for reporting this problem. (CVE-2026-14663)
Fix psql to skip in-line data following a scripted COPY ... FROM STDIN command, even if the COPY fails before sending PGRES_COPY_IN (Tom Lane) § §
Previously, if a COPY command failed at startup (for instance, because the target table doesn't exist) psql would not realize that and would proceed to read the following in-line data as SQL commands. In the best case that's wrong and in the worst case it's a SQL-injection hazard. Teach psql to recognize syntactically-valid COPY ... FROM STDIN commands and to skip data on its own authority if the server doesn't respond with PGRES_COPY_IN.
While this fix is unlikely to affect any production SQL scripts, test scripts might intentionally exercise failing COPY ... FROM STDIN commands. Those will need to gain a \. data terminator line after each such command.
The PostgreSQL Project thanks Alexander Lakhin for reporting this problem. (CVE-2026-6464)
Cross-check the output row type of a portal running EXECUTE or FETCH (Robert Haas) §
EXECUTE and FETCH use two portals: an outer one for the statement itself, and an inner one running the query being executed on its behalf. It was previously possible to make the declared row types of the two portals diverge, leading to server memory disclosure and arbitrary code execution.
The PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) and Peter Geoghegan for reporting this problem. (CVE-2026-16239)
Fix buffer overrun with long time zone abbreviation in to_char() (Tom Lane) §
This can easily crash the server, and exploits leading to arbitrary code execution have been reported.
The PostgreSQL Project thanks Hcamael, Amjad Shahzad, Tan Zhen of AntAISecurityLab, Tomer Fichman, Zheng Yu, Amy Burnett (OpenAI Codex Security), Rick de Jager, Heewon Song, Sylvie Mayer, Aleksander Alekseev, and Hillai Ben Sasson for reporting this problem. (CVE-2026-14669)
Fix buffer overrun in regexp match/split functions (Masahiko Sawada) §
If passed invalidly-encoded data, these functions could write past the end of their conversion buffer.
The PostgreSQL Project thanks Francesco Verardi for reporting this problem. (CVE-2026-14664)
Harden the ascii() function against invalid input (Michael Paquier) §
By supplying invalidly-encoded input, this function could be coaxed to read and return a few bytes of data that it shouldn't. In assert-enabled builds, its assertions could be triggered too.
The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-18024)
Fix multirange type handling in pg_restore_attribute_stats() (OpenAI Security Research Team) § §
pg_restore_attribute_stats() treated multirange types just like their underlying range type. This works correctly for the bounds histogram, but it was wrong for all the other statistics kinds.
The PostgreSQL Project thanks Amy Burnett (OpenAI Codex Security) for reporting this problem. (CVE-2026-16238)
Make scalarineqsel() check that a constant it expects to be of type tid actually is (Tom Lane) §
This expectation will hold for all the built-in operators that use this estimator, but a maliciously-constructed operator could violate it, leading to a crash or server memory disclosure.
The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14668)
Harden tsvector and tsquery code against overly long values (both individual lexemes and total vector/query length) (Tom Lane) § §
The documented limits were not enforced in all code paths.
The PostgreSQL Project thanks Yuhang Wu, Zhenpeng Lin, Zheng Yu, and Hcamael for reporting these problems. (CVE-2026-14662)
Fix various places that mistakenly assumed they would not have to deal with more than FUNC_MAX_ARGS function arguments (Tom Lane) § §
Notably, the server's actual limit on the number of arguments to an aggregate function is FUNC_MAX_ARGS - 1, but the parser failed to enforce that, creating hazards downstream.
The PostgreSQL Project thanks Zheng Yu, ylwangtju, and Masahiko Sawada for reporting these problems. (CVE-2026-14679)
Reject calls from SQL to functions that take or return type internal (Tom Lane) § §
The existing defenses against doing this have been shown to be insufficient, so add more explicit checks.
The PostgreSQL Project thanks Amy Burnett (OpenAI Codex Security) for reporting this problem. (CVE-2026-14680)
Preserve the ownership of extended statistics objects when they are rebuilt by ALTER TABLE (Masahiko Sawada) §
Previously, the role running ALTER TABLE gained ownership of such objects, but that seems inappropriate.
The PostgreSQL Project thanks Noah Misch for reporting this problem. (CVE-2026-6469)
When deparsing an EXTRACT() function call, quote the field name if needed (Nathan Bossart) §
The parser accepts any string literal as a field name in EXTRACT(), deferring validation to execution. If the call is stored and deparsed (for example during pg_dump), the string body was regurgitated verbatim, allowing SQL injection.
The PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-15741)
Check for USAGE privilege on data types in places that formerly failed to check that (Nathan Bossart) § § §
CREATE TYPE AS RANGE did not check, nor did ALTER TABLE OF, nor did commands that create stored expressions. These omissions allowed roles without USAGE privilege to nonetheless create objects depending on the type, possibly blocking the type's owner from changing the type later.
The PostgreSQL Project thanks Jingzhou Fu for reporting this problem. (CVE-2026-6470)
Invalidate role-dependent cached plans after role changes (Ilya Staroverov, Shinya Kato, Nathan Bossart) §
Role membership, role attribute, and database ownership changes may impact the expected behavior of row-level security policies, but previously we'd continue to use cached plans that were made according to the old state of affairs.
The PostgreSQL Project thanks Ilya Staroverov and Shinya Kato for reporting this problem. (CVE-2026-14666)
Reject GSSEncRequest after direct SSL connection (Michael Paquier) §
After establishing a TLS-encrypted connection, the server would still accept a request for GSSAPI encryption. If that succeeded, the connection would proceed using TLS encryption, but it would look like a GSS connection to the pg_hba rules. Thus, a pg_hba policy intending to disallow TLS would not be enforced correctly.
The PostgreSQL Project thanks p4p3r for reporting this problem. (CVE-2026-14681)
Make mock SCRAM authentication secrets more plausible (Nathan Bossart) §
If a SCRAM login is attempted against a role that doesn't exist or doesn't have a SCRAM secret, we generate a mock secret and carry out the authentication handshake anyway, to avoid revealing these facts to an attacker. But the mock secret was made with a fixed iteration count, which in itself can be an observable response discrepancy. Use the configuration setting scram_iterations instead, to make the mock secret look more like the installation's real secrets.
The PostgreSQL Project thanks Radim Marek for reporting this problem. (CVE-2026-14672)
Fix out-of-bounds writes in ecpg applications caused by invalid bytea data received from the server (Michael Paquier) §
ecpg assumed without checking that any bytea value must begin with \x. A broken or malicious server might send a string shorter than 2 bytes, resulting in memory clobber in the application.
The PostgreSQL Project thanks ylwangtju for reporting this problem. (CVE-2026-16241)
Do not do backquote expansion on the argument of psql's \unrestrict command (Nathan Bossart) §
This oversight in the fix for CVE-2025-8714 allows a malicious server to inject shell commands into plain-text dump output that will be run at restore time on the machine running psql, the exact scenario that CVE-2025-8714 intended to prevent.
The PostgreSQL Project thanks Lucas Velgus, Filip Janus, and Daniel Bakker for reporting this problem. (CVE-2026-18408)
Remove pg_dump's assumption that pg_proc.protrftypes cannot have more than FUNC_MAX_ARGS entries (Tom Lane) §
Since there could be entries for both input and output arguments, it's feasible for this array's length to exceed FUNC_MAX_ARGS (which constrains only input arguments). Even if that were not so, pg_dump cannot assume that the server was built with the same value of FUNC_MAX_ARGS that it has. An overrun would lead to a memory clobber inside pg_dump.
The PostgreSQL Project thanks Masahiko Sawada for reporting this problem. (CVE-2026-19385)
Harden PL/Perl against “tied” Perl arrays and hashes (Tom Lane) §
A tied object that doesn't behave like a regular one could lead to memory overwrite, or to constructing a corrupt result array (which would likely cause problems later).
The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14670)
Fix integer overflows in memory-allocation calculations in PL/Perl and PL/Tcl (Heikki Linnakangas) §
This is the same type of problem as CVE-2026-6473, just in a different part of the code, and is fixed in the same way.
The PostgreSQL Project thanks the Tulya Project (Team Dhiutsa, Bitecope Technologies Private Ltd) for reporting this problem. (CVE-2026-14677)
Ensure that contrib/amcheck functions restrict search_path before executing index expressions (Noah Misch) §
Because amcheck will run such index expressions as the owner of their tables, a caller could potentially hijack search_path-dependent functions to run arbitrary code as the table owner. By default this is not a vulnerability because only superusers are allowed to call amcheck functions; but if that privilege was granted out, it created a larger hazard than the documentation suggests.
The PostgreSQL Project thanks Yuelin Wang and Jacob Brazeal for reporting this problem. (CVE-2026-14673)
Fix integer overflows in contrib/fuzzystrmatch's levenshtein() and levenshtein_less_equal() functions (Nathan Bossart) §
Passing large cost values to these functions could cause integer overflows, thereby producing nonsensical results, and even causing out-of-bounds writes in some cases.
The PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-15742)
Fix buffer overrun in contrib/pg_stat_statements (Álvaro Herrera) §
Query normalization didn't accurately account for the amount of space the normalized string would require.
The PostgreSQL Project thanks Sajeeb Lohani (with TrendAI Zero Day Initiative) and Yuelin Wang for reporting this problem. (CVE-2026-14676)
Fix datatype error in contrib/pg_trgm's GiST picksplit function (Heikki Linnakangas) §
This mistake resulted in reading past the end of the buffer, typically causing bad split decisions; but a crash could ensue if you're very unlucky.
The PostgreSQL Project thanks Mehmet D. Ince for reporting this problem. (CVE-2026-14678)
Remove the plan cache in contrib/refint (Ayush Tiwari) §
This caching behavior has several serious bugs, notably that check_foreign_key() embeds the new key values in its cascade-UPDATE queries, so a cached plan reuses the originally-needed values rather than the key values that should be used. The simplest solution is to remove it.
The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14671)
Avoid NULL-pointer dereference in contrib/refint's check_foreign_key() (Ayush Tiwari) §
In the on-update-cascade case, a null value of a referenced column led to a crash. This is an oversight in the fix for CVE-2026-6637, but the code that was there before that wasn't really right either.
| Config parameter: | Default value: |
|---|---|
| db_user_namespace | off |
| old_snapshot_threshold | -1 |
| ssl_ecdh_curve | none |
| trace_recovery_messages | log |
| Config parameter: | Default value in Pg 16.14: | Default value in Pg 18.6: |
|---|---|---|
| data_checksums | off | on |
| effective_io_concurrency | 1 | 16 |
| log_connections | off | |
| maintenance_io_concurrency | 10 | 16 |
| shared_memory_size | 143 | 150 |
| shared_memory_size_in_huge_pages | 72 | 75 |
| vacuum_buffer_usage_limit | 256 | 2048 |
⇑ Upgrade to 17 released on 2024-09-26 - docs
Change functions to use a safe search_path during maintenance operations (Jeff Davis) §
This prevents maintenance operations (ANALYZE, CLUSTER, REFRESH MATERIALIZED VIEW, REINDEX, or VACUUM) from performing unsafe access. Functions used by expression indexes and materialized views that need to reference non-default schemas must specify a search path during function creation.
Restrict ago to only appear at the end in interval values (Joseph Koshakow) § §
Also, prevent empty interval units from appearing multiple times.
Remove server variable old_snapshot_threshold (Thomas Munro) §
This variable allowed vacuum to remove rows that potentially could be still visible to running transactions, causing "snapshot too old" errors later if accessed. This feature might be re-added to PostgreSQL later if an improved implementation is found.
Change SET SESSION AUTHORIZATION handling of the initial session user's superuser status (Joseph Koshakow) §
The new behavior is based on the session user's superuser status at the time the SET SESSION AUTHORIZATION command is issued, rather than their superuser status at connection time.
Remove feature which simulated per-database users (Nathan Bossart) §
The feature, db_user_namespace, was rarely used.
Remove wal_sync_method value fsync_writethrough on Windows (Thomas Munro) §
This value was the same as fsync on Windows.
Change file boundary handling of two WAL file name functions (Kyotaro Horiguchi, Andres Freund, Bruce Momjian) §
The functions pg_walfile_name() and pg_walfile_name_offset() used to report the previous LSN segment number when the LSN was on a file segment boundary; it now returns the current LSN segment.
Remove server variable trace_recovery_messages since it is no longer needed (Bharath Rupireddy) §
Remove information schema column element_types.domain_default (Peter Eisentraut) §
Change pgrowlocks lock mode output labels (Bruce Momjian) §
Remove buffers_backend and buffers_backend_fsync from pg_stat_bgwriter (Bharath Rupireddy) §
These fields are considered redundant to similar columns in pg_stat_io.
Rename I/O block read/write timing statistics columns of pg_stat_statements (Nazir Bilal Yavuz) §
This renames blk_read_time to shared_blk_read_time, and blk_write_time to shared_blk_write_time.
Change pg_attribute.attstattarget and pg_statistic_ext.stxstattarget to represent the default statistics target as NULL (Peter Eisentraut) § §
Rename pg_collation.colliculocale to colllocale and pg_database.daticulocale to datlocale (Jeff Davis) §
Rename pg_stat_progress_vacuum column max_dead_tuples to max_dead_tuple_bytes, rename num_dead_tuples to num_dead_item_ids, and add dead_tuple_bytes (Masahiko Sawada) § §
Rename SLRU columns in system view pg_stat_slru (Alvaro Herrera) §
The column names accepted by pg_stat_reset_slru() are also changed.
Allow the optimizer to improve CTE plans by considering the statistics and sort order of columns referenced in earlier row output clauses (Jian Guo, Richard Guo, Tom Lane) § §
Improve optimization of IS NOT NULL and IS NULL query restrictions (David Rowley, Richard Guo, Andy Fan) § §
Remove IS NOT NULL restrictions from queries on NOT NULL columns and eliminate scans on NOT NULL columns if IS NULL is specified.
Allow partition pruning on boolean columns on IS [NOT] UNKNOWN conditionals (David Rowley) §
Improve optimization of range values when using containment operators <@ and @> (Kim Johan Andersson, Jian He) §
Allow correlated IN subqueries to be transformed into joins (Andy Fan, Tom Lane) §
Improve optimization of the LIMIT clause on partitioned tables, inheritance parents, and UNION ALL queries (Andy Fan, David Rowley) §
Allow query nodes to be run in parallel in more cases (Tom Lane) §
Allow GROUP BY columns to be internally ordered to match ORDER BY (Andrei Lepikhov, Teodor Sigaev) §
This can be disabled using server variable enable_group_by_reordering.
Allow UNION (without ALL) to use MergeAppend (David Rowley) §
Fix MergeAppend plans to more accurately compute the number of rows that need to be sorted (Alexander Kuzmenkov) §
Allow GiST and SP-GiST indexes to be part of incremental sorts (Miroslav Bendik) §
This is particularly useful for ORDER BY clauses where the first column has a GiST and SP-GiST index, and other columns do not.
Add columns to pg_stats to report range-type histogram information (Egor Rogov, Soumyadeep Chakraborty) §
Allow btree indexes to more efficiently find a set of values, such as those supplied by IN clauses using constants (Peter Geoghegan, Matthias van de Meent) §
Allow BRIN indexes to be created using parallel workers (Tomas Vondra, Matthias van de Meent) §
Allow vacuum to more efficiently remove and freeze tuples (Melanie Plageman, Heikki Linnakangas) §
WAL traffic caused by vacuum is also more compact.
Allow vacuum to more efficiently store tuple references (Masahiko Sawada, John Naylor) § § § §
Additionally, vacuum is no longer silently limited to one gigabyte of memory when maintenance_work_mem or autovacuum_work_mem are higher.
Optimize vacuuming of relations with no indexes (Melanie Plageman) §
Increase default vacuum_buffer_usage_limit to 2MB (Thomas Munro) §
Improve performance when checking roles with many memberships (Nathan Bossart) §
Improve performance of heavily-contended WAL writes (Bharath Rupireddy) §
Improve performance when transferring large blocks of data to a client (Melih Mutlu) §
Allow the grouping of file system reads with the new system variable io_combine_limit (Thomas Munro, Andres Freund, Melanie Plageman, Nazir Bilal Yavuz) § § §
Create system view pg_stat_checkpointer (Bharath Rupireddy, Anton A. Melnikov, Alexander Korotkov) § § §
Relevant columns have been removed from pg_stat_bgwriter and added to this new system view.
Improve control over resetting statistics (Atsushi Torikoshi, Bharath Rupireddy) § § §
Allow pg_stat_reset_shared() (with no arguments) and pg_stat_reset_shared(NULL) to reset all shared statistics. Allow pg_stat_reset_shared('slru') and pg_stat_reset_slru() (with no arguments) to reset SLRU statistics, which was already possible with pg_stat_reset_slru(NULL).
Add log messages related to WAL recovery from backups (Andres Freund) §
Add log_connections log line for trust connections (Jacob Champion) §
Add log message to report walsender acquisition and release of replication slots (Bharath Rupireddy) §
This is enabled by the server variable log_replication_commands.
Add system view pg_wait_events that reports wait event types (Bertrand Drouvot) §
This is useful for adding descriptions to wait events reported in pg_stat_activity.
Add wait events for checkpoint delays (Thomas Munro) §
Allow vacuum to report the progress of index processing (Sami Imseih) §
This appears in system view pg_stat_progress_vacuum columns indexes_total and indexes_processed.
Allow granting the right to perform maintenance operations (Nathan Bossart) §
The permission can be granted on a per-table basis using the MAINTAIN privilege and on a per-role basis via the pg_maintain predefined role. Permitted operations are VACUUM, ANALYZE, REINDEX, REFRESH MATERIALIZED VIEW, CLUSTER, and LOCK TABLE.
Allow roles with pg_monitor membership to execute pg_current_logfile() (Pavlo Golub, Nathan Bossart) §
Add system variable allow_alter_system to disallow ALTER SYSTEM (Jelte Fennema-Nio, Gabriele Bartolini) §
Allow ALTER SYSTEM to set unrecognized custom server variables (Tom Lane) §
This is also possible with GRANT ON PARAMETER.
Add server variable transaction_timeout to restrict the duration of transactions (Andrey Borodin, Japin Li, Junwang Zhao, Alexander Korotkov) § § §
Add a builtin platform-independent collation provider (Jeff Davis) § § § §
This supports C and C.UTF-8 collations.
Add server variable huge_pages_status to report the use of huge pages by Postgres (Justin Pryzby) §
This is useful when huge_pages is set to try.
Add server variable to disable event triggers (Daniel Gustafsson) §
The setting, event_triggers, allows for the temporary disabling of event triggers for debugging.
Allow the SLRU cache sizes to be configured (Andrey Borodin, Dilip Kumar, Alvaro Herrera) §
The new server variables are commit_timestamp_buffers, multixact_member_buffers, multixact_offset_buffers, notify_buffers, serializable_buffers, subtransaction_buffers, and transaction_buffers. commit_timestamp_buffers, transaction_buffers, and subtransaction_buffers scale up automatically with shared_buffers.
Add support for incremental file system backup (Robert Haas, Jakub Wartak, Tomas Vondra) § §
Incremental backups can be created using pg_basebackup's new --incremental option. The new application pg_combinebackup allows manipulation of base and incremental file system backups.
Allow the creation of WAL summarization files (Robert Haas, Nathan Bossart, Hubert Depesz Lubaczewski) § § § §
These files record the block numbers that have changed within an LSN range and are useful for incremental file system backups. This is controlled by the server variables summarize_wal and wal_summary_keep_time, and introspected with pg_available_wal_summaries(), pg_wal_summary_contents(), and pg_get_wal_summarizer_state().
Add the system identifier to file system backup manifest files (Amul Sul) §
This helps detect invalid WAL usage.
Allow connection string value dbname to be written when pg_basebackup writes connection information to postgresql.auto.conf (Vignesh C, Hayato Kuroda) §
Add column pg_replication_slots.invalidation_reason to report the reason for invalid slots (Shveta Malik, Bharath Rupireddy) § §
Add column pg_replication_slots.inactive_since to report slot inactivity duration (Bharath Rupireddy) § § §
Add function pg_sync_replication_slots() to synchronize logical replication slots (Hou Zhijie, Shveta Malik, Ajin Cherian, Peter Eisentraut) § §
Add the failover property to the replication protocol (Hou Zhijie, Shveta Malik) §
Add application pg_createsubscriber to create a logical replica from a physical standby server (Euler Taveira) §
Have pg_upgrade migrate valid logical slots and subscriptions (Hayato Kuroda, Hou Zhijie, Vignesh C, Julien Rouhaud, Shlok Kyal) § §
This allows logical replication to continue quickly after the upgrade. This only works for old PostgreSQL clusters that are version 17 or later.
Enable the failover of logical slots (Hou Zhijie, Shveta Malik, Ajin Cherian) §
This is controlled by an optional fifth argument to pg_create_logical_replication_slot().
Add server variable sync_replication_slots to enable failover logical slot synchronization (Shveta Malik, Hou Zhijie, Peter Smith) § §
Add logical replication failover control to CREATE/ALTER SUBSCRIPTION (Shveta Malik, Hou Zhijie, Ajin Cherian) § §
Allow the application of logical replication changes to use hash indexes on the subscriber (Hayato Kuroda) §
Previously only btree indexes could be used for this purpose.
Improve logical decoding performance in cases where there are many subtransactions (Masahiko Sawada) §
Restart apply workers if subscription owner's superuser privileges are revoked (Vignesh C) §
This forces reauthentication.
Add flush option to pg_logical_emit_message() (Michael Paquier) §
This makes the message durable.
Allow specification of physical standbys that must be synchronized before they are visible to subscribers (Hou Zhijie, Shveta Malik) § §
The new server variable is synchronized_standby_slots.
Add worker type column to pg_stat_subscription (Peter Smith) §
Add new COPY option ON_ERROR ignore to discard error rows (Damir Belyalov, Atsushi Torikoshi, Alex Shulgin, Jian He, Yugo Nagata) § § § §
The default behavior is ON_ERROR stop.
Add new COPY option LOG_VERBOSITY which reports COPY FROM ignored error rows (Bharath Rupireddy) §
Allow COPY FROM to report the number of skipped rows during processing (Atsushi Torikoshi) §
This appears in system view column pg_stat_progress_copy.tuples_skipped.
In COPY FROM, allow easy specification that all columns should be forced null or not null (Zhang Mingli) §
Allow partitioned tables to have identity columns (Ashutosh Bapat) §
Allow exclusion constraints on partitioned tables (Paul A. Jungwirth) §
As long as exclusion constraints compare partition key columns for equality, other columns can use exclusion constraint-specific comparisons.
Add clearer ALTER TABLE method to set a column to the default statistics target (Peter Eisentraut) §
The new syntax is ALTER TABLE ... SET STATISTICS DEFAULT; using SET STATISTICS -1 is still supported.
Allow ALTER TABLE to change a column's generation expression (Amul Sul) §
The syntax is ALTER TABLE ... ALTER COLUMN ... SET EXPRESSION.
Allow specification of table access methods on partitioned tables (Justin Pryzby, Soumyadeep Chakraborty, Michael Paquier) § §
Add DEFAULT setting for ALTER TABLE .. SET ACCESS METHOD (Michael Paquier) §
Add support for event triggers that fire at connection time (Konstantin Knizhnik, Mikhail Gribkov) §
Add event trigger support for REINDEX (Garrett Thornburg, Jian He) §
Allow parenthesized syntax for CLUSTER options if a table name is not specified (Nathan Bossart) §
Allow EXPLAIN to report optimizer memory usage (Ashutosh Bapat) §
The option is called MEMORY.
Add EXPLAIN option SERIALIZE to report the cost of converting data for network transmission (Stepan Rutz, Matthias van de Meent) §
Add local I/O block read/write timing statistics to EXPLAIN's BUFFERS output (Nazir Bilal Yavuz) §
Improve EXPLAIN's display of SubPlan nodes and output parameters (Tom Lane, Dean Rasheed) §
Add JIT deform_counter details to EXPLAIN (Dmitry Dolgov) §
Allow the interval data type to support +/-infinity values (Joseph Koshakow, Jian He, Ashutosh Bapat) §
Allow the use of an ENUM added via ALTER TYPE if the type was created in the same transaction (Tom Lane) §
This was previously disallowed.
Allow MERGE to modify updatable views (Dean Rasheed) §
Add WHEN NOT MATCHED BY SOURCE to MERGE (Dean Rasheed) §
WHEN NOT MATCHED on target rows was already supported.
Allow MERGE to use the RETURNING clause (Dean Rasheed) §
The new RETURNING function merge_action() reports on the DML that generated the row.
Add function JSON_TABLE() to convert JSON data to a table representation (Nikita Glukhov, Teodor Sigaev, Oleg Bartunov, Alexander Korotkov, Andrew Dunstan, Amit Langote, Jian He) § §
This function can be used in the FROM clause of SELECT queries as a tuple source.
Add SQL/JSON constructor functions JSON(), JSON_SCALAR(), and JSON_SERIALIZE() (Nikita Glukhov, Teodor Sigaev, Oleg Bartunov, Alexander Korotkov, Andrew Dunstan, Amit Langote) §
Add SQL/JSON query functions JSON_EXISTS(), JSON_QUERY(), and JSON_VALUE() (Nikita Glukhov, Teodor Sigaev, Oleg Bartunov, Alexander Korotkov, Andrew Dunstan, Amit Langote, Peter Eisentraut, Jian He) § § § § §
Add jsonpath methods to convert JSON values to other JSON data types (Jeevan Chalke) §
The jsonpath methods are .bigint(), .boolean(), .date(), .decimal([precision [, scale]]), .integer(), .number(), .string(), .time(), .time_tz(), .timestamp(), and .timestamp_tz().
Add to_timestamp() time zone format specifiers (Tom Lane) §
TZ accepts time zone abbreviations or numeric offsets, while OF accepts only numeric offsets.
Allow the session time zone to be specified by AS LOCAL (Vik Fearing) §
This is useful when converting adding and removing time zones from time stamps values, rather than specifying the literal session time zone.
Add functions uuid_extract_timestamp() and uuid_extract_version() to return UUID information (Andrey Borodin) §
Add functions to generate random numbers in a specified range (Dean Rasheed) §
The functions are random(min, max) and they take values of type integer, bigint, and numeric.
Add functions to convert integers to binary and octal strings (Eric Radman, Nathan Bossart) §
The functions are to_bin() and to_oct().
Add Unicode informational functions (Jeff Davis) §
Function unicode_version() returns the Unicode version, icu_unicode_version() returns the ICU version, and unicode_assigned() returns if the characters are assigned Unicode codepoints.
Add function xmltext() to convert text to a single XML text node (Jim Jones) §
Add function to_regtypemod() to return the type modifier of a type specification (David Wheeler, Erik Wienhold) §
Add pg_basetype() function to return a domain's base type (Steve Chavez) §
Add function pg_column_toast_chunk_id() to return a value's TOAST identifier (Yugo Nagata) §
This returns NULL if the value is not stored in TOAST.
Allow plpgsql %TYPE and %ROWTYPE specifications to represent arrays of non-array types (Quan Zongliang, Pavel Stehule) §
Allow plpgsql %TYPE specification to reference composite column (Tom Lane) §
Add libpq function to change role passwords (Joe Conway) §
The new function, PQchangePassword(), hashes the new password before sending it to the server.
Add libpq functions to close portals and prepared statements (Jelte Fennema-Nio) §
The functions are PQclosePrepared(), PQclosePortal(), PQsendClosePrepared(), and PQsendClosePortal().
Add libpq API which allows for blocking and non-blocking cancel requests, with encryption if already in use (Jelte Fennema-Nio) §
Previously only blocking, unencrypted cancel requests were supported.
Add libpq function PQsocketPoll() to allow polling of network sockets (Tristan Partin, Tom Lane) § §
Add libpq function PQsendPipelineSync() to send a pipeline synchronization point (Anton Kirilov) §
This is similar to PQpipelineSync() but it does not flush to the server unless the size threshold of the output buffer is reached.
Add libpq function PQsetChunkedRowsMode() to allow retrieval of results in chunks (Daniel Vérité) §
Allow TLS connections without requiring a network round-trip negotiation (Greg Stark, Heikki Linnakangas, Peter Eisentraut, Michael Paquier, Daniel Gustafsson) § § § § § § § §
This is enabled with the client-side option sslnegotiation=direct, requires ALPN, and only works on PostgreSQL 17 and later servers.
Improve psql display of default and empty privileges (Erik Wienhold, Laurenz Albe) §
Command \dp now displays (none) for empty privileges; default still displays as empty.
Have backslash commands honor \pset null (Erik Wienhold, Laurenz Albe) §
Previously \pset null was ignored.
Allow psql's \watch to stop after a minimum number of rows returned (Greg Sabino Mullane) §
The parameter is min_rows.
Allow psql connection attempts to be canceled with control-C (Tristan Partin) §
Allow psql to honor FETCH_COUNT for non-SELECT queries (Daniel Vérité) §
Improve psql tab completion (Dagfinn Ilmari Mannsåker, Gilles Darold, Christoph Heiss, Steve Chavez, Vignesh C, Pavel Borisov, Jian He) § § § § § § § §
Add application pg_walsummary to dump WAL summary files (Robert Haas) §
Allow pg_dump's large objects to be restorable in batches (Tom Lane) §
This allows the restoration of many large objects to avoid transaction limits and to be restored in parallel.
Add pg_dump option --exclude-extension (Ayush Vatsa) §
Allow pg_dump, pg_dumpall, and pg_restore to specify include/exclude objects in a file (Pavel Stehule, Daniel Gustafsson) §
The option is called --filter.
Add the --sync-method parameter to several client applications (Justin Pryzby, Nathan Bossart) §
The applications are initdb, pg_basebackup, pg_checksums, pg_dump, pg_rewind, and pg_upgrade.
Add pg_restore option --transaction-size to allow object restores in transaction batches (Tom Lane) §
This allows the performance benefits of transaction batches without the problems of excessively large transaction blocks.
Change pgbench debug mode option from -d to --debug (Greg Sabino Mullane) §
Option -d is now used for the database name, and the new --dbname option can be used as well.
Add pgbench option --exit-on-abort to exit after any client aborts (Yugo Nagata) §
Add pgbench command \syncpipeline to allow sending of sync messages (Anthonin Bonnefoy) §
Allow pg_archivecleanup to remove backup history files (Atsushi Torikoshi) §
The option is --clean-backup-history.
Add some long options to pg_archivecleanup (Atsushi Torikoshi) §
The long options are --debug, --dry-run, and --strip-extension.
Allow pg_basebackup and pg_receivewal to use dbname in their connection specification (Jelte Fennema-Nio) §
This is useful for connection poolers that are sensitive to the database name.
Add pg_upgrade option --copy-file-range (Thomas Munro) §
This is supported on Linux and FreeBSD.
Allow reindexdb --index to process indexes from different tables in parallel (Maxim Orlov, Svetlana Derevyanko, Alexander Korotkov) §
Allow reindexdb, vacuumdb, and clusterdb to process objects in all databases matching a pattern (Nathan Bossart) § § §
The new option --all controls this behavior.
Remove support for OpenSSL 1.0.1 (Michael Paquier) §
Allow tests to pass in OpenSSL FIPS mode (Peter Eisentraut) § §
Use CPU AVX-512 instructions for bit counting (Paul Amonson, Nathan Bossart, Ants Aasma) § §
Require LLVM version 10 or later (Thomas Munro) §
Use native CRC instructions on 64-bit LoongArch CPUs (Xudong Yang) §
Remove AIX support (Heikki Linnakangas) §
Remove the Microsoft Visual Studio-specific PostgreSQL build option (Michael Paquier) §
Meson is now the only available method for Visual Studio builds.
Remove configure option --disable-thread-safety (Thomas Munro, Heikki Linnakangas) § §
We now assume all supported platforms have sufficient thread support.
Remove configure option --with-CC (Heikki Linnakangas) §
Setting the CC environment variable is now the only supported method for specifying the compiler.
User-defined data type receive functions will no longer receive their data null-terminated (David Rowley) §
Add incremental JSON parser for use with huge JSON documents (Andrew Dunstan) §
Convert top-level README file to Markdown (Nathan Bossart) §
Remove no longer needed top-level INSTALL file (Tom Lane) §
Remove make's distprep option (Peter Eisentraut) §
Add make support for Android shared libraries (Peter Eisentraut) §
Add backend support for injection points (Michael Paquier) § § § §
This is used for server debugging and they must be enabled at server compile time.
Add dynamic shared memory registry (Nathan Bossart) §
This allows shared libraries which are not initialized at startup to coordinate dynamic shared memory access.
Fix emit_log_hook to use the same time value as other log records for the same query (Kambam Vinay, Michael Paquier) §
Improve documentation for using jsonpath for predicate checks (David Wheeler) §
Allow joins with non-join qualifications to be pushed down to foreign servers and custom scans (Richard Guo, Etsuro Fujita) §
Foreign data wrappers and custom scans will need to be modified to handle these cases.
Allow pushdown of EXISTS and IN subqueries to postgres_fdw foreign servers (Alexander Pyhalov) §
Increase the default foreign data wrapper tuple cost (David Rowley, Umair Shahid) § §
This value is used by the optimizer.
Allow dblink database operations to be interrupted (Noah Misch) §
Allow the creation of hash indexes on ltree columns (Tommy Pavlicek) §
This also enables hash join and hash aggregation on ltree columns.
Allow unaccent character translation rules to contain whitespace and quotes (Michael Paquier) §
The syntax for the unaccent.rules file has changed.
Allow amcheck to check for unique constraint violations using new option --checkunique (Anastasia Lubennikova, Pavel Borisov, Maxim Orlov) §
Allow citext tests to pass in OpenSSL FIPS mode (Peter Eisentraut) §
Allow pgcrypto tests to pass in OpenSSL FIPS mode (Peter Eisentraut) §
Remove adminpack contrib extension (Daniel Gustafsson) §
This was used by now end-of-life pgAdmin III.
Allow ALTER OPERATOR to set more optimization attributes (Tommy Pavlicek) §
This is useful for extensions.
Allow extensions to define custom wait events (Masahiro Ikeda) § § § §
Custom wait events have been added to postgres_fdw and dblink.
Add pg_buffercache function pg_buffercache_evict() to allow shared buffer eviction (Palak Chaturvedi, Thomas Munro) §
This is useful for testing.
Replace CALL parameters in pg_stat_statements with placeholders (Sami Imseih) §
Replace savepoint names stored in pg_stat_statements with placeholders (Greg Sabino Mullane) §
This greatly reduces the number of entries needed to record SAVEPOINT, RELEASE SAVEPOINT, and ROLLBACK TO SAVEPOINT commands.
Replace the two-phase commit GIDs stored in pg_stat_statements with placeholders (Michael Paquier) §
This greatly reduces the number of entries needed to record PREPARE TRANSACTION, COMMIT PREPARED, and ROLLBACK PREPARED.
Track DEALLOCATE in pg_stat_statements (Dagfinn Ilmari Mannsåker, Michael Paquier) §
DEALLOCATE names are stored in pg_stat_statements as placeholders.
Add local I/O block read/write timing statistics columns of pg_stat_statements (Nazir Bilal Yavuz) § §
The new columns are local_blk_read_time and local_blk_write_time.
Add JIT deform_counter details to pg_stat_statements (Dmitry Dolgov) §
Add optional fourth argument (minmax_only) to pg_stat_statements_reset() to allow for the resetting of only min/max statistics (Andrei Zubkov) §
This argument defaults to false.
Add pg_stat_statements columns stats_since and minmax_stats_since to track entry creation time and last min/max reset time (Andrei Zubkov) §
⇑ Upgrade to 17.1 released on 2024-11-14 - docs
Prevent trusted PL/Perl code from changing environment variables (Andrew Dunstan, Noah Misch) § § §
The ability to manipulate process environment variables such as PATH gives an attacker opportunities to execute arbitrary code. Therefore, “trusted” PLs must not offer the ability to do that. To fix plperl, replace %ENV with a tied hash that rejects any modification attempt with a warning. Untrusted plperlu retains the ability to change the environment.
The PostgreSQL Project thanks Coby Abrams for reporting this problem. (CVE-2024-10979)
Fix test for C locale when LC_COLLATE is different from LC_CTYPE (Jeff Davis) §
When using libc as the default collation provider, the test to see if C locale is in use for collation accidentally checked LC_CTYPE not LC_COLLATE. This has no impact in the typical case where those settings are the same, nor if both are not C (nor its alias POSIX). However, if LC_CTYPE is C while LC_COLLATE is some other locale, wrong query answers could ensue, and corruption of indexes on strings was possible. Users of databases with such settings should reindex affected indexes after installing this update. The converse case with LC_COLLATE being C while LC_CTYPE is some other locale would cause performance degradation, but no actual errors.
Avoid planner failure after converting an IS NULL test on a NOT NULL column to constant FALSE (Richard Guo) §
This bug typically led to errors such as “variable not found in subplan target lists”.
Avoid possible planner crash while inlining a SQL function whose arguments contain certain array-related constructs (Tom Lane, Nathan Bossart) §
Fix possible wrong answers or “wrong varnullingrels” planner errors for MERGE ... WHEN NOT MATCHED BY SOURCE actions (Dean Rasheed) § §
Fix edge case in B-tree ScalarArrayOp index scans (Peter Geoghegan) §
When a scrollable cursor with a plan of this kind was backed up to its starting point and then run forward again, wrong answers were possible.
Fix validation of COPY's FORCE_NOT_NULL and FORCE_NULL options (Joel Jacobson) §
Some incorrect usages are now rejected as they should be.
Avoid crash when ALTER DATABASE SET is used to set a server parameter that requires search-path-based lookup, such as default_text_search_config (Jeff Davis) §
Avoid repeated lookups of opclasses and collations while creating a new index on a partitioned table (Tom Lane) §
This was problematic mainly because some of the lookups would be done with a restricted search_path, leading to unexpected failures if the CREATE INDEX command referenced objects outside pg_catalog.
This fix also prevents comments on the parent partitioned index from being copied to child indexes.
Add missing dependency from a partitioned table to a non-built-in access method specified in CREATE TABLE ... USING (Michael Paquier) §
Dropping the access method should be blocked when a table exists that depends on it, but it was not, allowing subsequent odd behavior. Note that this fix only prevents problems for partitioned tables created after this update.
Fix psql's describe commands to again work with pre-9.4 servers (Tom Lane) §
Commands involving display of an ACL (permissions) column failed with very old PostgreSQL servers, due to use of a function not present in those versions.
Fix failure to find replication password in ~/.pgpass (Tom Lane) §
pg_basebackup and pg_receivewal failed to match an entry in ~/.pgpass that had replication in the database name field, if no -d or --dbname switch was supplied. This resulted in an unexpected prompt for password.
In pg_combinebackup, throw an error if an incremental backup file is present in a directory that is supposed to contain a full backup (Robert Haas) §
In pg_combinebackup, don't construct filenames containing double slashes (Robert Haas) §
This caused no functional problems, but the duplicate slashes were visible in error messages, which could create confusion.
⇑ Upgrade to 17.2 released on 2024-11-21 - docs
⇑ Upgrade to 17.3 released on 2025-02-13 - docs
Restore auto-truncation of database and user names appearing in connection requests (Nathan Bossart) §
This reverts a v17 change that proved to cause trouble for some users. Over-length names should be truncated in an encoding-aware fashion, but for now just return to the former behavior of blind truncation at NAMEDATALEN-1 bytes.
Drop “Lock” suffix from LWLock wait event names (Bertrand Drouvot) §
Refactoring unintentionally caused the pg_stat_activity view to show lock-related wait event names with a “Lock” suffix, which among other things broke joining it to pg_wait_events.
Fix possible failure to return all matching tuples for a btree index scan with a ScalarArrayOp (= ANY) condition (Peter Geoghegan) §
Prevent possible catalog corruption when a system catalog is vacuumed concurrently with an update (Noah Misch) § §
Fix pg_get_constraintdef's support for NOT NULL constraints on domains (Álvaro Herrera) §
When deparsing a PASSING clause in a SQL/JSON query function, ensure that variable names are double-quoted when necessary (Dean Rasheed) §
Fix planning of pre-sorted UNION operations for cases where the input column datatypes don't all match (David Rowley) §
This error could lead to sorting data with the wrong sort operator, with consequences ranging from no visible problem to core dumps.
Give the slotsync worker process its own process slot (Tom Lane, Hou Zhijie) §
This was overlooked in the addition of the slotsync worker, with the result that its process slot effectively came out of the pool meant for regular backend processes. This could result in failure to launch the worker, or to subsequent failures of connection requests that should have succeeded according to the configured settings, if the number of regular backend processes approached max_connections.
Correct miscalculation of SLRU bank numbers (Yura Sokolov) §
This error led to using a smaller number of banks than intended, causing more contention but no functional misbehavior.
Avoid crash when a background process tries to check a new value of synchronized_standby_slots (Álvaro Herrera) §
Avoid potential use-after-free in parallel vacuum (Vallimaharajan G, John Naylor) §
This bug seems to have no consequences in standard builds, but it's theoretically a hazard.
Avoid valgrind complaints about string hashing code (John Naylor) §
Avoid data loss when starting a bulk write on a relation fork that already contains data (Matthias van de Meent) §
Any pre-existing data was overwritten with zeroes. This is not an issue for core PostgreSQL, which never does that. Some extensions would like to, however.
Avoid crash if a server process tried to iterate over a shared radix tree that it didn't create (Masahiko Sawada) §
There is no code in core PostgreSQL that does this, but an extension might wish to.
Add psql tab completion for COPY (MERGE INTO) (Jian He) §
Detect version mismatch between contrib/pageinspect's SQL declarations and the underlying shared library (Tomas Vondra) §
Previously, such a mismatch could result in a crash while calling brin_page_items(). Instead throw an error recommending updating the extension.
When trying to cancel a remote query in contrib/postgres_fdw, re-issue the cancel request a few times if it didn't seem to do anything (Tom Lane) §
This fixes a race condition where we might try to cancel a just-sent query before the remote server has started to process it, so that the initial cancel request is ignored.
⇑ Upgrade to 17.4 released on 2025-02-20 - docs
Fix small memory leak in pg_createsubscriber (Ranier Vilela) §
⇑ Upgrade to 17.5 released on 2025-05-08 - docs
Fix misprocessing of casts within the keys of JSON constructor expressions (Amit Langote) §
Fix erroneous deductions from column NOT NULL constraints in the presence of outer joins (Richard Guo) §
In some cases the planner would discard an IS NOT NULL query condition, even though the condition applies after an outer join and thus is not redundant.
Avoid incorrect optimizations based on IS [NOT] NULL tests that are applied to composite values (Bruce Momjian) §
Fix incorrect table size estimate with low fill factor (Tomas Vondra) §
When the planner estimates the number of rows in a never-yet-analyzed table, it uses the table's fillfactor setting in the estimation, but it neglected to clamp the result to at least one row per page. A low fillfactor could thus result in an unreasonably small estimate.
Cope with possible intra-query changes of io_combine_limit (Thomas Munro) §
Fix over-enthusiastic freeing of SpecialJoinInfo structs during planning (Richard Guo) §
This led to crashes during planning if partitionwise joining is enabled.
Fix crash in logical replication if the subscriber's partitioned table has a BRIN index (Tom Lane) §
Fix order of operations in smgropen() (Andres Freund) §
Ensure that the SMgrRelation object is fully initialized before calling the smgr_open callback, so that it can be cleaned up properly if the callback fails.
Avoid assertion failure in parallel vacuum when maintenance_work_mem has a very small value (Masahiko Sawada) §
Fix reindexdb's scheduling of parallel reindex operations (Alexander Korotkov) §
The original coding failed to achieve the expected amount of parallelism.
In contrib/postgres_fdw, avoid pulling up restriction conditions from subqueries (Alexander Pyhalov) §
This fix prevents rare cases of “unexpected expression in subquery output” errors.
Fix build failure when an old version of libpq_fe.h is present in system include directories (Tom Lane) §
Fix valgrind labeling of per-buffer data of read streams (Thomas Munro) §
This affects no core code in released versions of PostgreSQL, but an extension using the per-buffer data feature might have encountered spurious failures when being tested under valgrind.
⇑ Upgrade to 17.6 released on 2025-08-14 - docs
Fix MERGE problems with concurrent updates (Dean Rasheed) §
If a MERGE inside a CTE attempts an update or delete on a table with BEFORE ROW triggers, and a concurrent UPDATE or DELETE changes the target row, the MERGE command would fail (crashing in the case of an update action, and potentially executing the wrong action in the case of a delete action).
Ensure that the table's free-space map is updated in a timely way when vacuuming a table that has no indexes (Masahiko Sawada) §
A previous optimization caused FSM vacuuming to sometimes be skipped for such tables.
Fix inconsistent spelling of LWLock names for MultiXactOffsetSLRU and MultiXactMemberSLRU (Bertrand Drouvot) §
This resulted in different wait-event names being displayed in pg_wait_events and pg_stat_activity, potentially breaking monitoring queries that join those views.
Avoid unexpected server shutdown when replication slot synchronization is misconfigured (Fujii Masao) §
The postmaster process would report an error (and then stop) if sync_replication_slots was set to true while wal_level was less than logical. The desired behavior is just that slot synchronization should be disabled, so reduce this error message's level to avoid postmaster shutdown.
Fix possible crash after out-of-memory when allocating large chunks with the “bump” allocator (Tom Lane) §
Fix libpq's PQcancelCreate() function for the case where the server's address was specified using hostaddr (Sergei Kornilov) §
libpq would crash if the resulting cancel object was actually used.
Fix duplicate transaction replay when initializing a subscription with pg_createsubscriber (Shlok Kyal) §
It was possible for the last transaction processed during subscriber recovery to be sent again once normal replication begins.
Ensure that pg_dump dumps comments on not-null constraints on domain types (Jian He, Álvaro Herrera) §
Fix incorrect parsing of object types in pg_dump filter files (Fujii Masao) §
Treat keywords as extending to the next whitespace, rather than stopping at the first non-alphanumeric character as before. This makes no difference for valid keywords, but it allows some error cases to be recognized properly. For example, table-data will now be rejected, whereas previously it was misinterpreted as table.
pg_restore failed to restore large objects (BLOBs) from directory-format dumps made by pg_dump versions before PostgreSQL v12 (Pavel Stehule) §
In pg_upgrade, check for inconsistent inherited not-null constraints (Ali Akbar) § § §
PostgreSQL versions before 18 allow an inherited column not-null constraint to be dropped. However, this results in a schema that cannot be restored, leading to failure in pg_upgrade. Detect such cases during pg_upgrade's preflight checks to allow users to fix them before initiating the upgrade.
Don't require that the target installation have max_slot_wal_keep_size set to its default during pg_upgrade (Dilip Kumar) §
Prevent assertion failure in contrib/pg_prewarm (Masahiro Ikeda) §
Applying pg_prewarm() to a relation lacking storage (such as a view) caused an assertion failure, although there was no ill effect in non-assert builds. Add an error check to reject that case.
Make our usage of memset_s() conform strictly to the C11 standard (Tom Lane) §
This avoids compile failures on some platforms.
⇑ Upgrade to 18 released on 2025-09-25 - docs
Change initdb default to enable data checksums (Greg Sabino Mullane) §
Checksums can be disabled with the new initdb option --no-data-checksums. pg_upgrade requires matching cluster checksum settings, so this new option can be useful to upgrade non-checksum old clusters.
Change time zone abbreviation handling (Tom Lane) §
The system will now favor the current session's time zone abbreviations before checking the server variable timezone_abbreviations. Previously timezone_abbreviations was checked first.
Deprecate MD5 password authentication (Nathan Bossart) §
Support for MD5 passwords will be removed in a future major version release. CREATE ROLE and ALTER ROLE now emit deprecation warnings when setting MD5 passwords. These warnings can be disabled by setting the md5_password_warnings parameter to off.
Change VACUUM and ANALYZE to process the inheritance children of a parent (Michael Harris) §
The previous behavior can be performed by using the new ONLY option.
Prevent COPY FROM from treating \. as an end-of-file marker when reading CSV files (Daniel Vérité, Tom Lane) § §
psql will still treat \. as an end-of-file marker when reading CSV files from STDIN. Older psql clients connecting to PostgreSQL 18 servers might experience \copy problems. This release also enforces that \. must appear alone on a line.
Disallow unlogged partitioned tables (Michael Paquier) §
Previously ALTER TABLE SET [UN]LOGGED did nothing, and the creation of an unlogged partitioned table did not cause its children to be unlogged.
Execute AFTER triggers as the role that was active when trigger events were queued (Laurenz Albe) §
Previously such triggers were run as the role that was active at trigger execution time (e.g., at COMMIT). This is significant for cases where the role is changed between queue time and transaction commit.
Remove non-functional support for rule privileges in GRANT/REVOKE (Fujii Masao) §
These have been non-functional since PostgreSQL 8.2.
Remove column pg_backend_memory_contexts.parent (Melih Mutlu) §
This is no longer needed since pg_backend_memory_contexts.path was added.
Change pg_backend_memory_contexts.level and pg_log_backend_memory_contexts() to be one-based (Melih Mutlu, Atsushi Torikoshi, David Rowley, Fujii Masao) § § §
These were previously zero-based.
Change full text search to use the default collation provider of the cluster to read configuration files and dictionaries, rather than always using libc (Peter Eisentraut) §
Clusters that default to non-libc collation providers (e.g., ICU, builtin) that behave differently than libc for characters processed by LC_CTYPE could observe changes in behavior of some full-text search functions, as well as the pg_trgm extension. When upgrading such clusters using pg_upgrade, it is recommended to reindex all indexes related to full-text search and pg_trgm after the upgrade.
Automatically remove some unnecessary table self-joins (Andrey Lepikhov, Alexander Kuzmenkov, Alexander Korotkov, Alena Rybakina) §
This optimization can be disabled using server variable enable_self_join_elimination.
Convert some IN (VALUES ...) to x = ANY ... for better optimizer statistics (Alena Rybakina, Andrei Lepikhov) §
Allow transforming OR-clauses to arrays for faster index processing (Alexander Korotkov, Andrey Lepikhov) §
Speed up the processing of INTERSECT, EXCEPT, window aggregates, and view column aliases (Tom Lane, David Rowley) § § § §
Allow the keys of SELECT DISTINCT to be internally reordered to avoid sorting (Richard Guo) §
This optimization can be disabled using enable_distinct_reordering.
Ignore GROUP BY columns that are functionally dependent on other columns (Zhang Mingli, Jian He, David Rowley) §
If a GROUP BY clause includes all columns of a unique index, as well as other columns of the same table, those other columns are redundant and can be dropped from the grouping. This was already true for non-deferred primary keys.
Allow some HAVING clauses on GROUPING SETS to be pushed to WHERE clauses (Richard Guo) § § § §
This allows earlier row filtering. This release also fixes some GROUPING SETS queries that used to return incorrect results.
Improve row estimates for generate_series() using numeric and timestamp values (David Rowley, Song Jinzhou) § §
Allow the optimizer to use Right Semi Join plans (Richard Guo) §
Semi-joins are used when needing to find if there is at least one match.
Allow merge joins to use incremental sorts (Richard Guo) §
Improve the efficiency of planning queries accessing many partitions (Ashutosh Bapat, Yuya Watari, David Rowley) § §
Allow partitionwise joins in more cases, and reduce its memory usage (Richard Guo, Tom Lane, Ashutosh Bapat) § §
Improve cost estimates of partition queries (Nikita Malakhov, Andrei Lepikhov) §
Improve SQL-language function plan caching (Alexander Pyhalov, Tom Lane) § §
Improve handling of disabled optimizer features (Robert Haas) §
Allow skip scans of btree indexes (Peter Geoghegan) § §
This allows multi-column btree indexes to be used in more cases such as when there are no restrictions on the first or early indexed columns (or there are non-equality ones), and there are useful restrictions on later indexed columns.
Allow non-btree unique indexes to be used as partition keys and in materialized views (Mark Dilger) § §
The index type must still support equality.
Allow GIN indexes to be created in parallel (Tomas Vondra, Matthias van de Meent) §
Allow values to be sorted to speed range-type GiST and btree index builds (Bernd Helmle) §
Add an asynchronous I/O subsystem (Andres Freund, Thomas Munro, Nazir Bilal Yavuz, Melanie Plageman) § § § § § § § § § § §
This feature allows backends to queue multiple read requests, which allows for more efficient sequential scans, bitmap heap scans, vacuums, etc. This is enabled by server variable io_method, with server variables io_combine_limit and io_max_combine_limit added to control it. This also enables effective_io_concurrency and maintenance_io_concurrency values greater than zero for systems without fadvise() support. The new system view pg_aios shows the file handles being used for asynchronous I/O.
Improve the locking performance of queries that access many relations (Tomas Vondra) §
Improve the performance and reduce memory usage of hash joins and GROUP BY (David Rowley, Jeff Davis) § § § § §
This also improves hash set operations used by EXCEPT, and hash lookups of subplan values.
Allow normal vacuums to freeze some pages, even though they are all-visible (Melanie Plageman) § §
This reduces the overhead of later full-relation freezing. The aggressiveness of this can be controlled by server variable and per-table setting vacuum_max_eager_freeze_failure_rate. Previously vacuum never processed all-visible pages until freezing was required.
Add server variable vacuum_truncate to control file truncation during VACUUM (Nathan Bossart, Gurjeet Singh) §
A storage-level parameter with the same name and behavior already existed.
Increase server variables effective_io_concurrency's and maintenance_io_concurrency's default values to 16 (Melanie Plageman) § §
This more accurately reflects modern hardware.
Increase the logging granularity of server variable log_connections (Melanie Plageman) §
This server variable was previously only boolean, which is still supported.
Add log_connections option to report the duration of connection stages (Melanie Plageman) §
Add log_line_prefix escape %L to output the client IP address (Greg Sabino Mullane) §
Add server variable log_lock_failures to log lock acquisition failures (Yuki Seino, Fujii Masao) § §
Specifically it reports SELECT ... NOWAIT lock failures.
Modify pg_stat_all_tables and its variants to report the time spent in VACUUM, ANALYZE, and their automatic variants (Sami Imseih) §
The new columns are total_vacuum_time, total_autovacuum_time, total_analyze_time, and total_autoanalyze_time.
Add delay time reporting to VACUUM and ANALYZE (Bertrand Drouvot, Nathan Bossart) § §
This information appears in the server log, the system views pg_stat_progress_vacuum and pg_stat_progress_analyze, and the output of VACUUM and ANALYZE when in VERBOSE mode; tracking must be enabled with the server variable track_cost_delay_timing.
Add WAL, CPU, and average read statistics output to ANALYZE VERBOSE (Anthonin Bonnefoy) § §
Add full WAL buffer count to VACUUM/ANALYZE (VERBOSE) and autovacuum log output (Bertrand Drouvot) §
Add per-backend I/O statistics reporting (Bertrand Drouvot) § §
The statistics are accessed via pg_stat_get_backend_io(). Per-backend I/O statistics can be cleared via pg_stat_reset_backend_stats().
Add pg_stat_io columns to report I/O activity in bytes (Nazir Bilal Yavuz) §
The new columns are read_bytes, write_bytes, and extend_bytes. The op_bytes column, which always equaled BLCKSZ, has been removed.
Add WAL I/O activity rows to pg_stat_io (Nazir Bilal Yavuz, Bertrand Drouvot, Michael Paquier) § § §
This includes WAL receiver activity and a wait event for such writes.
Change server variable track_wal_io_timing to control tracking WAL timing in pg_stat_io instead of pg_stat_wal (Bertrand Drouvot) §
Remove read/sync columns from pg_stat_wal (Bertrand Drouvot) § §
This removes columns wal_write, wal_sync, wal_write_time, and wal_sync_time.
Add function pg_stat_get_backend_wal() to return per-backend WAL statistics (Bertrand Drouvot) §
Per-backend WAL statistics can be cleared via pg_stat_reset_backend_stats().
Add function pg_ls_summariesdir() to specifically list the contents of PGDATA/pg_wal/summaries (Yushi Ogiwara) §
Add column pg_stat_checkpointer.num_done to report the number of completed checkpoints (Anton A. Melnikov) §
Columns num_timed and num_requested count both completed and skipped checkpoints.
Add column pg_stat_checkpointer.slru_written to report SLRU buffers written (Nitin Jadhav) §
Also, modify the checkpoint server log message to report separate shared buffer and SLRU buffer values.
Add columns to pg_stat_database to report parallel worker activity (Benoit Lobréau) §
The new columns are parallel_workers_to_launch and parallel_workers_launched.
Have query id computation of constant lists consider only the first and last constants (Dmitry Dolgov, Sami Imseih) § § §
Jumbling is used by pg_stat_statements.
Adjust query id computations to group together queries using the same relation name (Michael Paquier, Sami Imseih) §
This is true even if the tables in different schemas have different column names.
Add column pg_backend_memory_contexts.type to report the type of memory context (David Rowley) §
Add column pg_backend_memory_contexts.path to show memory context parents (Melih Mutlu) §
Add function pg_get_acl() to retrieve database access control details (Joel Jacobson) § §
Add function has_largeobject_privilege() to check large object privileges (Yugo Nagata) §
Allow ALTER DEFAULT PRIVILEGES to define large object default privileges (Takatsuka Haruka, Yugo Nagata, Laurenz Albe) §
Add predefined role pg_signal_autovacuum_worker (Kirill Reshke) §
This allows sending signals to autovacuum workers.
Add support for the OAuth authentication method (Jacob Champion, Daniel Gustafsson, Thomas Munro) §
This adds an oauth authentication method to pg_hba.conf, libpq OAuth options, a server variable oauth_validator_libraries to load token validation libraries, and a configure flag --with-libcurl to add the required compile-time libraries.
Add server variable ssl_tls13_ciphers to allow specification of multiple colon-separated TLSv1.3 cipher suites (Erica Zhang, Daniel Gustafsson) §
Change server variable ssl_groups's default to include elliptic curve X25519 (Daniel Gustafsson, Jacob Champion) §
Rename server variable ssl_ecdh_curve to ssl_groups and allow multiple colon-separated ECDH curves to be specified (Erica Zhang, Daniel Gustafsson) §
The previous name still works.
Make cancel request keys 256 bits (Heikki Linnakangas, Jelte Fennema-Nio) § §
This is only possible when the server and client support wire protocol version 3.2, introduced in this release.
Add server variable autovacuum_worker_slots to specify the maximum number of background workers (Nathan Bossart) §
With this variable set, autovacuum_max_workers can be adjusted at runtime up to this maximum without a server restart.
Allow specification of the fixed number of dead tuples that will trigger an autovacuum (Nathan Bossart, Frédéric Yhuel) §
The server variable is autovacuum_vacuum_max_threshold. Percentages are still used for triggering.
Change server variable max_files_per_process to limit only files opened by a backend (Andres Freund) §
Previously files opened by the postmaster were also counted toward this limit.
Add server variable num_os_semaphores to report the required number of semaphores (Nathan Bossart) §
This is useful for operating system configuration.
Add server variable extension_control_path to specify the location of extension control files (Peter Eisentraut, Matheus Alcantara) § §
Allow inactive replication slots to be automatically invalidated using server variable idle_replication_slot_timeout (Nisha Moond, Bharath Rupireddy) §
Add server variable max_active_replication_origins to control the maximum active replication origins (Euler Taveira) §
This was previously controlled by max_replication_slots, but this new setting allows a higher origin count in cases where fewer slots are required.
Allow the values of generated columns to be logically replicated (Shubham Khanna, Vignesh C, Zhijie Hou, Shlok Kyal, Peter Smith) § § § §
If the publication specifies a column list, all specified columns, generated and non-generated, are published. Without a specified column list, publication option publish_generated_columns controls whether generated columns are published. Previously generated columns were not replicated and the subscriber had to compute the values if possible; this is particularly useful for non-PostgreSQL subscribers which lack such a capability.
Change the default CREATE SUBSCRIPTION streaming option from off to parallel (Vignesh C) §
Allow ALTER SUBSCRIPTION to change the replication slot's two-phase commit behavior (Hayato Kuroda, Ajin Cherian, Amit Kapila, Zhijie Hou) § §
Log conflicts while applying logical replication changes (Zhijie Hou, Nisha Moond) § § § § §
Also report in new columns of pg_stat_subscription_stats.
Allow generated columns to be virtual, and make them the default (Peter Eisentraut, Jian He, Richard Guo, Dean Rasheed) § § §
Virtual generated columns generate their values when the columns are read, not written. The write behavior can still be specified via the STORED option.
Add OLD/NEW support to RETURNING in DML queries (Dean Rasheed) §
Previously RETURNING only returned new values for INSERT and UPDATE, and old values for DELETE; MERGE would return the appropriate value for the internal query executed. This new syntax allows the RETURNING list of INSERT/UPDATE/DELETE/MERGE to explicitly return old and new values by using the special aliases old and new. These aliases can be renamed to avoid identifier conflicts.
Allow foreign tables to be created like existing local tables (Zhang Mingli) §
The syntax is CREATE FOREIGN TABLE ... LIKE.
Allow LIKE with nondeterministic collations (Peter Eisentraut) §
Allow text position search functions with nondeterministic collations (Peter Eisentraut) §
These used to generate an error.
Add builtin collation provider PG_UNICODE_FAST (Jeff Davis) §
This locale supports case mapping, but sorts in code point order, not natural language order.
Allow VACUUM and ANALYZE to process partitioned tables without processing their children (Michael Harris) §
This is enabled with the new ONLY option. This is useful since autovacuum does not process partitioned tables, just its children.
Add functions to modify per-relation and per-column optimizer statistics (Corey Huinker) § § §
The functions are pg_restore_relation_stats(), pg_restore_attribute_stats(), pg_clear_relation_stats(), and pg_clear_attribute_stats().
Add server variable file_copy_method to control the file copying method (Nazir Bilal Yavuz) §
This controls whether CREATE DATABASE ... STRATEGY=FILE_COPY and ALTER DATABASE ... SET TABLESPACE uses file copy or clone.
Allow the specification of non-overlapping PRIMARY KEY, UNIQUE, and foreign key constraints (Paul A. Jungwirth) § §
This is specified by WITHOUT OVERLAPS for PRIMARY KEY and UNIQUE, and by PERIOD for foreign keys, all applied to the last specified column.
Allow CHECK and foreign key constraints to be specified as NOT ENFORCED (Amul Sul) § §
This also adds column pg_constraint.conenforced.
Require primary/foreign key relationships to use either deterministic collations or the the same nondeterministic collations (Peter Eisentraut) §
The restore of a pg_dump, also used by pg_upgrade, will fail if these requirements are not met; schema changes must be made for these upgrade methods to succeed.
Store column NOT NULL specifications in pg_constraint (Álvaro Herrera, Bernd Helmle) § §
This allows names to be specified for NOT NULL constraint. This also adds NOT NULL constraints to foreign tables and NOT NULL inheritance control to local tables.
Allow ALTER TABLE to set the NOT VALID attribute of NOT NULL constraints (Rushabh Lathia, Jian He) §
Allow modification of the inheritability of NOT NULL constraints (Suraj Kharage, Álvaro Herrera) § §
The syntax is ALTER TABLE ... ALTER CONSTRAINT ... [NO] INHERIT.
Allow NOT VALID foreign key constraints on partitioned tables (Amul Sul) §
Allow dropping of constraints ONLY on partitioned tables (Álvaro Herrera) §
This was previously erroneously prohibited.
Add REJECT_LIMIT to control the number of invalid rows COPY FROM can ignore (Atsushi Torikoshi) §
This is available when ON_ERROR = 'ignore'.
Allow COPY TO to copy rows from populated materialized views (Jian He) §
Add COPY LOG_VERBOSITY level silent to suppress log output of ignored rows (Atsushi Torikoshi) §
This new level suppresses output for discarded input rows when on_error = 'ignore'.
Disallow COPY FREEZE on foreign tables (Nathan Bossart) §
Previously, the COPY worked but the FREEZE was ignored, so disallow this command.
Automatically include BUFFERS output in EXPLAIN ANALYZE (Guillaume Lelarge, David Rowley) §
Add full WAL buffer count to EXPLAIN (WAL) output (Bertrand Drouvot) §
In EXPLAIN ANALYZE, report the number of index lookups used per index scan node (Peter Geoghegan) §
Modify EXPLAIN to output fractional row counts (Ibrar Ahmed, Ilia Evdokimov, Robert Haas) § §
Add memory and disk usage details to Material, Window Aggregate, and common table expression nodes to EXPLAIN output (David Rowley, Tatsuo Ishii) § § § §
Add details about window function arguments to EXPLAIN output (Tom Lane) §
Add Parallel Bitmap Heap Scan worker cache statistics to EXPLAIN ANALYZE (David Geier, Heikki Linnakangas, Donghang Lin, Alena Rybakina, David Rowley) §
Indicate disabled nodes in EXPLAIN ANALYZE output (Robert Haas, David Rowley, Laurenz Albe) § § §
Improve Unicode full case mapping and conversion (Jeff Davis) § §
This adds the ability to do conditional and title case mapping, and case map single characters to multiple characters.
Allow jsonb null values to be cast to scalar types as NULL (Tom Lane) §
Previously such casts generated an error.
Add optional parameter to json{b}_strip_nulls to allow removal of null array elements (Florents Tselai) §
Add function array_sort() which sorts an array's first dimension (Junwang Zhao, Jian He) §
Add function array_reverse() which reverses an array's first dimension (Aleksander Alekseev) §
Add function reverse() to reverse bytea bytes (Aleksander Alekseev) §
Allow casting between integer types and bytea (Aleksander Alekseev) §
The integer values are stored as bytea two's complement values.
Improve the XML error codes to more closely match the SQL standard (Tom Lane) §
These errors are reported via SQLSTATE.
Add function casefold() to allow for more sophisticated case-insensitive matching (Jeff Davis) §
This allows more accurate comparisons, i.e., a character can have multiple upper or lower case equivalents, or upper or lower case conversion changes the number of characters.
Allow MIN()/MAX() aggregates on arrays and composite types (Aleksander Alekseev, Marat Buharov) § §
Improve the output EXTRACT(QUARTER ...) for negative values (Tom Lane) §
Add roman numeral support to to_number() (Hunaid Sohail) §
This is accessed via the RN pattern.
Add UUID version 7 generation function uuidv7() (Andrey Borodin) §
This UUID value is temporally sortable. Function alias uuidv4() has been added to explicitly generate version 4 UUIDs.
Add functions crc32() and crc32c() to compute CRC values (Aleksander Alekseev) §
Allow => syntax for named cursor arguments in PL/pgSQL (Pavel Stehule) §
We previously only accepted :=.
Allow regexp_match[es]()/regexp_like()/regexp_replace()/regexp_count()/regexp_instr()/regexp_substr()/regexp_split_to_table()/regexp_split_to_array() to use named arguments (Jian He) §
Add function PQfullProtocolVersion() to report the full, including minor, protocol version number (Jacob Champion, Jelte Fennema-Nio) §
Add libpq connection parameters and environment variables to specify the minimum and maximum acceptable protocol version for connections (Jelte Fennema-Nio) § §
Report search_path changes to the client (Alexander Kukushkin, Jelte Fennema-Nio, Tomas Vondra) § §
Add PQtrace() output for all message types, including authentication (Jelte Fennema-Nio) § § § § §
Add libpq connection parameter sslkeylogfile which dumps out SSL key material (Abhishek Chanda, Daniel Gustafsson) §
This is useful for debugging.
Modify some libpq function signatures to use int64_t (Thomas Munro) §
These previously used pg_int64, which is now deprecated.
Allow psql to parse, bind, and close named prepared statements (Anthonin Bonnefoy, Michael Paquier) § §
This is accomplished with new commands \parse, \bind_named, and \close_prepared.
Add psql backslash commands to allowing issuance of pipeline queries (Anthonin Bonnefoy) § § §
The new commands are \startpipeline, \syncpipeline, \sendpipeline, \endpipeline, \flushrequest, \flush, and \getresults.
Allow adding pipeline status to the psql prompt and add related state variables (Anthonin Bonnefoy) §
The new prompt character is %P and the new psql variables are PIPELINE_SYNC_COUNT, PIPELINE_COMMAND_COUNT, and PIPELINE_RESULT_COUNT.
Allow adding the connection service name to the psql prompt or access it via psql variable (Michael Banck) §
Add psql option to use expanded mode on all list commands (Dean Rasheed) §
Adding backslash suffix x enables this.
Change psql's \conninfo to use tabular format and include more information (Álvaro Herrera, Maiquel Grassi, Hunaid Sohail) §
Add function's leakproof indicator to psql's \df+, \do+, \dAo+, and \dC+ outputs (Yugo Nagata) §
Add access method details for partitioned relations in \dP+ (Justin Pryzby) §
Add default_version to the psql \dx extension output (Magnus Hagander) §
Add psql variable WATCH_INTERVAL to set the default \watch wait time (Daniel Gustafsson) §
Change initdb to default to enabling checksums (Greg Sabino Mullane) § §
The new initdb option --no-data-checksums disables checksums.
Add initdb option --no-sync-data-files to avoid syncing heap/index files (Nathan Bossart) §
initdb option --no-sync is still available to avoid syncing any files.
Add vacuumdb option --missing-stats-only to compute only missing optimizer statistics (Corey Huinker, Nathan Bossart) § §
This option can only be run by superusers and can only be used with options --analyze-only and --analyze-in-stages.
Add pg_combinebackup option -k/--link to enable hard linking (Israel Barth Rubio, Robert Haas) §
Only some files can be hard linked. This should not be used if the backups will be used independently.
Allow pg_verifybackup to verify tar-format backups (Amul Sul) §
If pg_rewind's --source-server specifies a database name, use it in --write-recovery-conf output (Masahiko Sawada) §
Add pg_resetwal option --char-signedness to change the default char signedness (Masahiko Sawada) §
Add pg_dump and pg_dumpall option --sequence-data to dump sequence data that would normally be excluded (Nathan Bossart) § §
Add pg_dump, pg_dumpall, and pg_restore options --statistics-only, --no-statistics, --no-data, and --no-schema (Corey Huinker, Jeff Davis) §
Add option --no-policies to disable row level security policy processing in pg_dump, pg_dumpall, pg_restore (Nikolay Samokhvalov) §
This is useful for migrating to systems with different policies.
Allow pg_upgrade to preserve optimizer statistics (Corey Huinker, Jeff Davis, Nathan Bossart) § § § §
Extended statistics are not preserved. Also add pg_upgrade option --no-statistics to disable statistics preservation.
Allow pg_upgrade to process database checks in parallel (Nathan Bossart) § § § § § § § § § § §
This is controlled by the existing --jobs option.
Add pg_upgrade option --swap to swap directories rather than copy, clone, or link files (Nathan Bossart) §
This mode is potentially the fastest.
Add pg_upgrade option --set-char-signedness to set the default char signedness of new cluster (Masahiko Sawada) § §
This is to handle cases where a pre-PostgreSQL 18 cluster's default CPU signedness does not match the new cluster.
Add pg_createsubscriber option --all to create logical replicas for all databases (Shubham Khanna) §
Add pg_createsubscriber option --clean to remove publications (Shubham Khanna) § §
Add pg_createsubscriber option --enable-two-phase to enable prepared transactions (Shubham Khanna) §
Add pg_recvlogical option --enable-failover to specify failover slots (Hayato Kuroda) §
Also add option --enable-two-phase as a synonym for --two-phase, and deprecate the latter.
Allow pg_recvlogical --drop-slot to work without --dbname (Hayato Kuroda) §
Separate the loading and running of injection points (Michael Paquier, Heikki Linnakangas) § §
Injection points can now be created, but not run, via INJECTION_POINT_LOAD(), and such injection points can be run via INJECTION_POINT_CACHED().
Support runtime arguments in injection points (Michael Paquier) §
Allow inline injection point test code with IS_INJECTION_POINT_ATTACHED() (Heikki Linnakangas) §
Improve the performance of processing long JSON strings using SIMD (Single Instruction Multiple Data) (David Rowley) §
Speed up CRC32C calculations using x86 AVX-512 instructions (Raghuveer Devulapalli, Paul Amonson) §
Add ARM Neon and SVE CPU intrinsics for popcount (integer bit counting) (Chiranmoy Bhattacharya, Devanga Susmitha, Rama Malladi) § §
Improve the speed of numeric multiplication and division (Joel Jacobson, Dean Rasheed) § § § §
Add configure option --with-libnuma to enable NUMA awareness (Jakub Wartak, Bertrand Drouvot) § § §
The function pg_numa_available() reports on NUMA awareness, and system views pg_shmem_allocations_numa and pg_buffercache_numa which report on shared memory distribution across NUMA nodes.
Add TOAST table to pg_index to allow for very large expression indexes (Nathan Bossart) §
Remove column pg_attribute.attcacheoff (David Rowley) §
Add amgettreeheight, amconsistentequality, and amconsistentordering to the index access method API (Mark Dilger) § §
Add GiST support function stratnum() (Paul A. Jungwirth) §
Record the default CPU signedness of char in pg_controldata (Masahiko Sawada) §
Add support for Python "Limited API" in PL/Python (Peter Eisentraut) § §
This helps prevent problems caused by Python 3.x version mismatches.
Change the minimum supported Python version to 3.6.8 (Jacob Champion) §
Remove support for OpenSSL versions older than 1.1.1 (Daniel Gustafsson) § §
If LLVM is enabled, require version 14 or later (Thomas Munro) §
Add macro PG_MODULE_MAGIC_EXT to allow extensions to report their name and version (Andrei Lepikhov) §
This information can be access via the new function pg_get_loaded_modules().
Document that SPI_connect()/SPI_connect_ext() always returns success (SPI_OK_CONNECT) (Stepan Neretin) §
Errors are always reported via ereport().
Add documentation section about API and ABI compatibility (David Wheeler, Peter Eisentraut) §
Remove the experimental designation of Meson builds on Windows (Aleksander Alekseev) §
Remove configure options --disable-spinlocks and --disable-atomics (Thomas Munro) § §
Thirty-two-bit atomic operations are now required.
Remove support for the HPPA/PA-RISC architecture (Tom Lane) §
Add extension pg_logicalinspect to inspect logical snapshots (Bertrand Drouvot) §
Add extension pg_overexplain which adds debug details to EXPLAIN output (Robert Haas) §
Add output columns to postgres_fdw_get_connections() (Hayato Kuroda, Sagar Dilip Shedge) § § § §
New output column used_in_xact indicates if the foreign data wrapper is being used by a current transaction, closed indicates if it is closed, user_name indicates the user name, and remote_backend_pid indicates the remote backend process identifier.
Allow SCRAM authentication from the client to be passed to postgres_fdw servers (Matheus Alcantara, Peter Eisentraut) §
This avoids storing postgres_fdw authentication information in the database, and is enabled with the postgres_fdw use_scram_passthrough connection option. libpq uses new connection parameters scram_client_key and scram_server_key.
Allow SCRAM authentication from the client to be passed to dblink servers (Matheus Alcantara) §
Add on_error and log_verbosity options to file_fdw (Atsushi Torikoshi) §
These control how file_fdw handles and reports invalid file rows.
Add reject_limit to control the number of invalid rows file_fdw can ignore (Atsushi Torikoshi) §
This is active when ON_ERROR = 'ignore'.
Add configurable variable min_password_length to passwordcheck (Emanuele Musella, Maurizio Boriani) §
This controls the minimum password length.
Have pgbench report the number of failed, retried, or skipped transactions in per-script reports (Yugo Nagata) §
Add isn server variable weak to control invalid check digit acceptance (Viktor Holmberg) §
This was previously only controlled by function isn_weak().
Allow values to be sorted to speed btree_gist index builds (Bernd Helmle, Andrey Borodin) §
Add amcheck check function gin_index_check() to verify GIN indexes (Grigory Kryachko, Heikki Linnakangas, Andrey Borodin) §
Add functions pg_buffercache_evict_relation() and pg_buffercache_evict_all() to evict unpinned shared buffers (Nazir Bilal Yavuz) §
The existing function pg_buffercache_evict() now returns the buffer flush status.
Allow extensions to install custom EXPLAIN options (Robert Haas, Sami Imseih) § § §
Allow extensions to use the server's cumulative statistics API (Michael Paquier) § §
Allow the queries of CREATE TABLE AS and DECLARE to be tracked by pg_stat_statements (Anthonin Bonnefoy) §
They are also now assigned query ids.
Allow the parameterization of SET values in pg_stat_statements (Greg Sabino Mullane, Michael Paquier) §
This reduces the bloat caused by SET statements with differing constants.
Add pg_stat_statements columns to report parallel activity (Guillaume Lelarge) §
The new columns are parallel_workers_to_launch and parallel_workers_launched.
Add pg_stat_statements.wal_buffers_full to report full WAL buffers (Bertrand Drouvot) §
Add pgcrypto algorithms sha256crypt and sha512crypt (Bernd Helmle) §
Add CFB mode to pgcrypto encryption and decryption (Umar Hayat) §
Add function fips_mode() to report the server's FIPS mode (Daniel Gustafsson) §
Add pgcrypto server variable builtin_crypto_enabled to allow disabling builtin non-FIPS mode cryptographic functions (Daniel Gustafsson, Joe Conway) §
This is useful for guaranteeing FIPS mode behavior.
⇑ Upgrade to 18.1 released on 2025-11-13 - docs
Prevent “unrecognized node type” errors when a SQL/JSON function such as JSON_VALUE has a DEFAULT clause containing a COLLATE expression (Jian He) § §
Avoid incorrect optimization of variable-free HAVING clauses with grouping sets (Richard Guo) § §
Do not use parallelism in hash right semi joins (Richard Guo) §
The case does not work reliably due to a race condition in updating the join's shared hash table.
Avoid possible division-by-zero when creating ordered-append plans (Richard Guo) §
This mistake could result in incorrect selection of the cheapest path, or in an assertion failure in debug builds.
Fix planner failure with index types that can do ordered access but not index-only scans (Maxime Schoemans) §
This oversight resulted in errors like “no data returned for index-only scan”. The case does not arise with any in-core index type, but some extensions encountered the problem.
Avoid possible out-of-memory or “invalid memory alloc request size” failures during parallel GIN index build (Tomas Vondra) §
Fix rare crash when processing hashed GROUPING SETS queries (David Rowley) §
Repair faulty hash-table-size-choosing logic in hash joins (Tomas Vondra) §
Hash joins sometimes used more memory than intended, or failed to divide it in an efficient way.
Improve relation lookup logic in statistics manipulation functions (Nathan Bossart) § §
Fix pg_restore_relation_stats(), pg_clear_relation_stats(), pg_restore_attribute_stats(), and pg_clear_attribute_stats() to check privileges before acquiring lock on the target relation rather than after.
Fix crash during EvalPlanQual rechecks on partitioned tables (David Rowley, Amit Langote) §
Prevent setting a column as identity if it has a not-null constraint but the constraint is marked as invalid (Jian He) §
Identity columns must be not-null, but the check for that missed this edge case.
Avoid potential use-after-free in parallel vacuum (Kevin Oommen Anish) §
This bug seems to have no consequences in standard builds, but it's theoretically a hazard.
Avoid failures when synchronized_standby_slots references nonexistent replication slots (Shlok Kyal) §
Re-establish special case for C collation in locale setup (Jeff Davis) §
This fixes a regression in access to shared catalogs early in backend startup, before a database has been selected. It is not known to be a problem for any core PostgreSQL code, but some extensions were broken.
Fix dumping of non-inherited not-null constraints on inherited table columns (Dilip Kumar) §
pg_dump failed to preserve such constraints when dumping from a pre-v18 server.
Fix pg_dump's sorting of foreign key constraints (Álvaro Herrera) §
Ensure consistent ordering of these database objects, as was already done for other object types.
Fix per-file memory leakage in pg_combinebackup (Tom Lane) §
Ensure that contrib/pg_buffercache functions can be canceled (Satyanarayana Narlapuram, Yuhang Qiu) § §
Some code paths were capable of running for a long time without checking for interrupts.
In contrib/pg_stat_statements, avoid crash when two or more constants are marked as having the same location in the SQL statement text (Sami Imseih, Dmitry Dolgov) §
⇑ Upgrade to 18.2 released on 2026-02-12 - docs
Harden selectivity estimators against being attached to operators that accept unexpected data types (Tom Lane) § §
contrib/intarray contained a selectivity estimation function that could be abused for arbitrary code execution, because it did not check that its input was of the expected data type. Third-party extensions should check for similar hazards and add defenses using the technique intarray now uses. Since such extension fixes will take time, we now require superuser privilege to attach a non-built-in selectivity estimator to an operator.
The PostgreSQL Project thanks Daniel Firer, as part of zeroday.cloud, for reporting this problem. (CVE-2026-2004)
Harden contrib/pg_trgm against changes in string lowercasing behavior (Heikki Linnakangas) § §
Fix potential buffer overruns arising from the fact that in some locales lower-casing a string can produce more characters (not bytes) than were in the original. That behavior is new in version 18, and so is the bug.
The PostgreSQL Project thanks Heikki Linnakangas for reporting this problem. (CVE-2026-2007)
Fix inconsistent case-insensitive matching in contrib/ltree (Jeff Davis) § §
Index-related routines in ltree used a different implementation of case-folding than the primary operators did. Their behavior was equivalent only if the default collation provider was libc and the encoding was single-byte.
To fix, change the code to use case-folding with the database's default collation. This change will require reindexing indexes on ltree columns (regardless of the index access method) unless the database uses libc as collation provider and its encoding is single-byte. Without that, searches of such indexes will fail to locate relevant entries.
When using ALTER TABLE ... ADD CONSTRAINT to add a not-null constraint with an explicit name, if the column is already marked NOT NULL, require that the provided name match the existing constraint name (Álvaro Herrera, Srinath Reddy Sadipiralla) §
Fix incorrect pruning of rowmarks belonging to non-relation rangetable entries, such as subqueries (Dean Rasheed) §
This led to incorrect results if a proposed row update needed to be modified by EvalPlanQual rechecking, as could happen if there was a concurrent update to that row.
Fix expression evaluation bug for a sub-select within an array subscript (Andres Freund) §
Fix text substring search for non-deterministic collations (Laurenz Albe) §
When using a non-deterministic collation, we failed to detect a match occurring at the very end of the searched string.
Fix planner error with set-returning functions and grouping sets (Richard Guo) §
When constructing a ProjectSet plan node, the planner failed to detect that subexpressions involving grouping expressions were already computed by the input plan. This led to inefficient plans or errors such as “variable not found in subplan target list”.
Avoid incorrect optimization when a subquery's grouping clause contains a volatile or set-returning function (Richard Guo) §
The planner was willing to push down outer-query restrictions referencing such a grouping column, leading to incorrect behavior due to multiple evaluation of a volatile function, or errors caused by introduction of a set-returning function into the subquery's WHERE/HAVING clauses.
Look through PlaceHolderVar nodes when searching for statistics about an expression (Richard Guo) §
This change allows the planner to find relevant statistics about expressions pulled up from subqueries or used in GROUP BY, avoiding falling back to a default estimate. (Arguably we should adjust any found statistics to account for an increased probability of the value being NULL, but we've never done the equivalent thing for plain Vars either.) While this restriction is old, changes in PostgreSQL version 18 made PlaceHolderVars more common than before, so make the change to avoid plan regressions in affected cases.
Look through no-op PlaceHolderVar nodes when matching expressions to indexes (Richard Guo) §
Because PostgreSQL version 18 uses PlaceHolderVars in more cases than before, some queries that formerly could use an index failed to do so. Add logic to prevent that regression.
Fix planner's conversion of OR clauses to ScalarArrayOp index conditions (Tender Wang, Tom Lane) §
The code did not handle RelabelType nodes correctly, and could generate invalid expressions or fail to perform a valid conversion.
Use the correct ordering function in parallel GIN index builds (Tomas Vondra) §
The parallel code used the default ordering operator (which is determined by the column data type's btree opclass), whereas it should use the ordering function specified by the GIN opclass, if any. This led to a failure if the data type has no btree opclass, or to an invalid index if the opclass specifies an ordering function that doesn't agree with the btree opclass.
Consider grouping expressions when computing a query ID hash (Jian He) §
Previously, two queries that were the same except in GROUP BY expressions would be merged by contrib/pg_stat_statements and other users of query IDs.
Fix erroneous counting of updates in EXPLAIN ANALYZE MERGE with a concurrent update (Dean Rasheed) §
This situation led to an incorrect count of “skipped” tuples in EXPLAIN's output, or to an assertion failure in an assert-enabled build.
Fix incorrect handling of incremental backups of large tables (Robert Haas, Oleg Tkachenko) §
If a table exceeding 1GB (or in general, the installation's segment size) is truncated by VACUUM between the base backup and the incremental backup, pg_combinebackup could fail with an error about “truncation block length in excess of segment size”. This prevented restoring the incremental backup.
Fix race condition in async I/O code (Andres Freund) §
It was possible for the result code of an asynchronous I/O operation to be overwritten before it was fetched.
Allow retrying initialization of a DSM registry entry (Nathan Bossart) §
If we fail partway through initialization of a dynamic shared memory entry, allow the next attempt to use that entry to retry initialization. Previously the entry was left in a permanently-failed state.
Avoid failure of NUMA status views when a page has been swapped out (Tomas Vondra) §
Avoid “operation not permitted” errors when querying NUMA page status with older libnuma versions (Tomas Vondra) §
Prevent invalidation of newly created or newly synced replication slots (Zhijie Hou) § § §
A race condition with a concurrent checkpoint could allow WAL to be removed that is needed by the replication slot, causing the slot to immediately get marked invalid.
Fix logical replication slotsync worker processes to handle LOCK_TIMEOUT signals correctly (Zhijie Hou) §
Previously, timeout signals were effectively ignored.
Fix error reporting for SQL/JSON path type mismatches (Jian He) §
The code could produce a “cache lookup failed for type 0” error instead of the intended complaint about the path expression not being of the right type.
Fix assorted minor errors in error messages (Man Zeng, Tianchen Zhang) § § § § §
For example, an error report about mismatched timeline number in a backup manifest showed the starting timeline number where it meant to show the ending timeline number.
Fix aarch64-specific code to build with old (RHEL7-era) system header files (Tom Lane) § §
Fix incorrect configure probe for io_uring_queue_init_mem() (Masahiko Sawada) §
This error resulted in failure to optimize async I/O buffer allocations in autotools-based builds, though the code did work when building with meson. The main impact of the omission was slower-than-necessary backend process exits.
Fix psql's tab completion for VACUUM option values (Yugo Nagata) §
In psql command prompts, do not show a value for %P (pipeline status) when there is no server connection (Chao Li) §
This makes %P act like other prompt escape sequences whose values depend on the active connection.
Fix pg_dump's logic for collecting sequence values (Nathan Bossart) § §
pg_dump failed if a sequence was dropped concurrently with the dump, even if the sequence was not among the database objects to be dumped. Also, if the calling user lacks privileges to read a sequence's value, pg_dump emitted incorrect values rather than failing as expected.
Fix potentially-incorrect quoting of oauth_validator_libraries values by pg_dump (ChangAo Chen) §
pg_dump applied the wrong quoting rule if it needed to dump a value of this setting.
Avoid pg_dump assertion failure in binary-upgrade mode (Vignesh C) §
Failure to handle subscription-relation objects in the object sorting code triggered an assertion, though there were no serious ill effects in production builds.
Fix incorrect error handling in pgbench with multiple \syncpipeline commands in pipeline mode (Yugo Nagata) §
If multiple \syncpipeline commands are encountered after a query error, pgbench would report “failed to exit pipeline mode”, or get an assertion failure in an assert-enabled build.
In contrib/amcheck, use the correct snapshot for btree index parent checks (Mihail Nikalayeu) § §
The previous coding caused spurious errors when examining indexes created with CREATE INDEX CONCURRENTLY.
Fix excessive memory allocation in contrib/pg_buffercache (David Geier) §
The code allocated twice as much memory as it needed for NUMA page status.
Avoid crash in contrib/pg_stat_statements when an IN list contains both constants and non-constant expressions (Sami Imseih) §
⇑ Upgrade to 18.3 released on 2026-02-26 - docs
Fix oversight in the fix for CVE-2026-2007 (Zsolt Parragi) §
If the “bounds” array needed to be expanded, because the input contained more trigrams than the initial guess, generate_trgm_only didn't return the modified array pointer to its caller. That would lead to incorrect output from strict_word_similarity() and related functions, or in rare cases a crash. The faulty code is reached if the input string becomes longer when it's converted to lower case. The only known instances of that occur when an ICU locale is used with certain single-byte encodings.
Fix the volatility marking of json_strip_nulls() and jsonb_strip_nulls() (Andrew Dunstan) §
These functions have always been considered immutable, but refactoring in version 18 accidentally marked them stable instead. That prevents their use in index expressions and could cause unnecessary repeat evaluations in queries. This fix corrects the marking in newly-initialized database clusters (including clusters that are pg_upgrade'd to 18.3 or later). However it will not help existing clusters made using 18.0 through 18.2.
If this mistake affects your usage of these functions, the recommended fix for an existing cluster is a manual catalog update. As superuser, perform
UPDATE pg_catalog.pg_proc SET provolatile = 'i' WHERE oid IN ('3261','3262');
in each affected database. Update template0 and template1 as well, so that databases made in future will have the fix.
Avoid name collisions between user-written constraints and automatically-named NOT NULL constraints (Laurenz Albe) §
As of version 18, NOT NULL constraints have full-fledged pg_constraint entries, and therefore require names. The logic for choosing a name for an unnamed NOT NULL constraint failed to avoid conflicts with user-written constraints elsewhere in the same CREATE TABLE statement.
⇑ Upgrade to 18.4 released on 2026-05-14 - docs
Prevent unbounded recursion while processing startup packets (Michael Paquier) §
A malicious client could crash the connected backend by alternating rejected SSL and GSS encryption requests indefinitely.
The PostgreSQL Project thanks Calif.io (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-6479)
Fix assorted integer overflows in memory-allocation calculations (Tom Lane, Nathan Bossart, Heikki Linnakangas) § § § § § § § § §
Various places were incautious about the possibility of integer overflow in calculations of how much memory to allocate. Overflow would lead to allocating a too-small buffer which the caller would then write past the end of. This would at least trigger server crashes, and probably could be exploited for arbitrary code execution. In many but by no means all cases, the hazard exists only in 32-bit builds.
The PostgreSQL Project thanks Xint Code, Bruce Dang, Sven Klemm, and Pavel Kohout for reporting these problems. (CVE-2026-6473)
Properly quote subscription names in pg_createsubscriber (Nathan Bossart) §
The given subscription name was inserted into SQL commands without quoting, so that SQL injection could be achieved in the (perhaps unlikely) case that the subscription name comes from an untrusted source.
The PostgreSQL Project thanks Yu Kunpeng for reporting this problem. (CVE-2026-6476)
Detect faulty input when restoring attribute MCV statistics (Michael Paquier) §
The statistics restore functions were insufficiently careful about validating most-common-value statistics, and would accept values that could crash the planner later on.
The PostgreSQL Project thanks Jeroen Gui for reporting this problem. (CVE-2026-6575)
Use timing-safe string comparisons in authentication code (Michael Paquier) §
Use timingsafe_bcmp() instead of memcpy() or strcmp() when checking passwords, hashes, etc. It is not known whether the data dependency of those functions is usefully exploitable in any of these places, but in the interests of safety, replace them.
The PostgreSQL Project thanks Joe Conway for reporting this problem. (CVE-2026-6478)
Check for nondeterministic collations before assuming that an equality condition on a collatable type implies uniqueness (Richard Guo) § § § § §
Numerous planner optimizations assume that, for example, at most one table row can satisfy WHERE x = 'abc' if there is a unique index on x. However this conclusion is unsafe in general if the index and the WHERE clause have different collations attached. It is safe when both collations are deterministic, because that property essentially requires that equality of two strings means bitwise equality. But nondeterministic collations don't act that way, so that optimizing on the assumption of unique matches can give wrong query answers if either the WHERE clause or the index has a nondeterministic collation.
Fix incomplete removal of relation references in RestrictInfo structs during join removal (Tom Lane) §
This oversight has been shown to result in planner failures such as unexpected “FULL JOIN is only supported with merge-joinable or hash-joinable join conditions” errors. It may also have caused failure to consider valid plans in other cases.
Improve planner's matching of partition key columns to sub-query outputs (Richard Guo) §
Strip no-op PlaceHolderVars from operands before comparing them to partition keys. This change enables partition pruning to succeed in some cases where it previously failed to recognize that a partition need not be scanned.
Fix self-join removal to handle join clauses that are bare boolean columns, e.g. ON t1.boolcol (Andrei Lepikhov, Tender Wang, Alexander Korotkov) §
Previously such a case led to a “no relation entry for relid N” error.
Fix UPDATE/DELETE ... WHERE CURRENT OF to work on tables with virtual generated columns (Satyanarayana Narlapuram, Dean Rasheed) §
Fix expansion of virtual generated columns in EXCLUDED column references in INSERT ... ON CONFLICT (Satyanarayana Narlapuram, Dean Rasheed) §
Fix spurious “indexes on virtual generated columns are not supported” errors (Robert Haas) §
Creation of an expression index could sometimes incorrectly report this error.
Fix ALTER TABLE ... SET NOT NULL to invoke object-access hook functions only after completing the catalog change (Artur Zakirov) §
Fix loss of deferrability of foreign-key triggers (Yasuo Honda) §
Previously, a foreign key defined as DEFERRABLE INITIALLY DEFERRED would behave as NOT DEFERRABLE after being set to NOT ENFORCED status and then back to ENFORCED.
If you have a foreign key with this problem, it can be repaired (after installing this update) by again setting it to NOT ENFORCED and then back to ENFORCED.
Fix WITHOUT OVERLAPS to allow domains (Jian He) §
UNIQUE/PRIMARY KEY ... WITHOUT OVERLAPS requires the no-overlap column to be a range or multirange, but it should allow a domain over such a type too.
Fix “no relation entry for relid 0” failure while estimating array lengths in set operations (Tender Wang) §
Fix incremental JSON parser's handling of numeric tokens that cross input buffer boundaries (Andrew Dunstan) §
It was possible to accept an incorrectly-formatted number, leading to failures later.
Prevent bloating relation visibility maps during restore of an incremental backup (Robert Haas) §
Restore could append many blocks of zeroes to a visibility map, due to incorrect computation of the expected file length. This does not result in data corruption, but it could waste a substantial amount of disk space.
Use C collation, not the database's default collation, in catalog cache lookups on text columns (Jeff Davis) §
This avoids failures in edge cases such as physical replication startup, where there is no identified database so that a default collation cannot be determined.
Prevent stuck slotsync worker processes from blocking promotion of a standby server (Nisha Moond, Ajin Cherian) § § §
A worker process that was vainly waiting for a response from the primary would delay promotion for an unreasonable amount of time.
Fix excessive log output from idle slotsync worker processes (Zhijie Hou) §
Make the pg_aios system view's pid column show NULL not 0 when an entry has no owning process (ChangAo Chen) §
Fix under-allocation of shared memory used for parallel btree index scans (Siddharth Kothari) §
In edge cases this could result in a server crash.
Fix indexing of oldest-multixact arrays in shared memory (Yura Sokolov) § §
This mistake could cause a prepared-but-not-yet-committed transaction's row locks to appear invisible to other sessions, or other visibility issues for the results of such a transaction. With a very small max_connections setting, memory stomps were also possible.
Fix array overrun when too many EXPLAIN extension options are installed (Joel Jacobson) §
Correctly display join alias Vars that are used in GROUP BY (Tom Lane) §
In views containing queries like SELECT ... t1 LEFT JOIN t2 USING (x) GROUP BY x, the GROUP BY clause could be displayed incorrectly by deparsing, leading to dump/restore failures. Failures occurred only if t1.x and t2.x were not of identical data types and t1.x was the side that required an implicit coercion.
Harden tar-file parsing logic against archives it can't handle (Tom Lane) §
The tar-file reading code used in pg_basebackup and pg_verifybackup failed to verify that the input is a tar file at all, let alone that it fits into the subset of valid tar files that we can handle. This isn't a problem for the normal scenario where the input file was generated by PostgreSQL code, but it can be an issue if the input has been generated by some other tar program.
In pg_dump, preserve NO INHERIT property of NOT NULL constraints (Jian He) §
Some cases missed printing the NO INHERIT clause.
Fix contrib/ltree to cope when case-folding changes a string's byte length (Jeff Davis) § §
Previously, lquery patterns specifying case-insensitive matching might fail to match labels they should match.
Fix mis-structured output from contrib/pg_overexplain's RANGE_TABLE option (Satyanarayana Narlapuram) §
Some fields were misplaced in JSON, YAML, and XML formats, resulting in structurally invalid output.
⇑ Upgrade to 18.6 released on 2026-08-13 - docs
Restrict logical decoding output plugins to the set specified by a new server parameter output_plugin_libraries (Jacob Champion) § §
Previously, a replication user could select any loadable library for logical decoding, allowing exploits of various sorts. To allow locking this down without breaking setups that worked before, introduce a whitelist of allowed output plugins.
By default, only the output plugins shipped as part of PostgreSQL (pgoutput and test_decoding) are included in output_plugin_libraries. Installations that rely on other output plugins must add them after updating the server, for example
output_plugin_libraries = 'pgoutput, test_decoding, my_trusted_decoder'
Additionally, pg_upgrade --check will fail if the output_plugin_libraries parameter on the new cluster does not permit the plugins of logical replication slots on the old cluster, when migrating from versions 17 and later. Make necessary additions to the new cluster's setting before performing pg_upgrade.
The PostgreSQL Project thanks Vladimir Tokarev and Yu Kunpeng for reporting this problem. (CVE-2026-6471)
Fix contrib/pgcrypto's PGP encryption to detect unsupported ciphers (Daniel Gustafsson) § §
Previously, if OpenSSL rejected the requested cipher (for example, because it is running in FIPS mode, or the legacy provider hasn't been loaded), pgcrypto failed to notice the failure and simply XOR'd the non-encrypted block with the plaintext, rendering the “encryption” trivially breakable. This will typically occur with deprecated or non-FIPS cipher algorithms (cipher-algo=blowfish/bf, twofish, cast5, or 3des).
By default, pgcrypto will now fail to decrypt any messages that were affected in this way. To allow retrieval of such data, a new option ignore-cipher-failure has been added to pgp_pub_decrypt() and pgp_sym_decrypt(). Setting ignore-cipher-failure=1 will restore their previous behavior, allowing the faulty encryption wrapper to be stripped off:
pgp_sym_decrypt(encrypted_column, any key, 'ignore-cipher-failure=1')
Once the affected messages are identified and stripped of their wrappers, they can then be re-encrypted with a modern algorithm. It is important however that the behavior of OpenSSL be the same as it was when the faulty messages were created: if the set of unsupported algorithms is not the same, this approach will not work. See the documentation for ignore-cipher-failure.
The PostgreSQL Project thanks Shishir Sharma for reporting this problem. (CVE-2026-14663)
Fix psql to skip in-line data following a scripted COPY ... FROM STDIN command, even if the COPY fails before sending PGRES_COPY_IN (Tom Lane) § §
Previously, if a COPY command failed at startup (for instance, because the target table doesn't exist) psql would not realize that and would proceed to read the following in-line data as SQL commands. In the best case that's wrong and in the worst case it's a SQL-injection hazard. Teach psql to recognize syntactically-valid COPY ... FROM STDIN commands and to skip data on its own authority if the server doesn't respond with PGRES_COPY_IN.
While this fix is unlikely to affect any production SQL scripts, test scripts might intentionally exercise failing COPY ... FROM STDIN commands. Those will need to gain a \. data terminator line after each such command.
The PostgreSQL Project thanks Alexander Lakhin for reporting this problem. (CVE-2026-6464)
Cross-check the output row type of a portal running EXECUTE or FETCH (Robert Haas) §
EXECUTE and FETCH use two portals: an outer one for the statement itself, and an inner one running the query being executed on its behalf. It was previously possible to make the declared row types of the two portals diverge, leading to server memory disclosure and arbitrary code execution.
The PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) and Peter Geoghegan for reporting this problem. (CVE-2026-16239)
Fix buffer overrun with long time zone abbreviation in to_char() (Tom Lane) §
This can easily crash the server, and exploits leading to arbitrary code execution have been reported.
The PostgreSQL Project thanks Hcamael, Amjad Shahzad, Tan Zhen of AntAISecurityLab, Tomer Fichman, Zheng Yu, Amy Burnett (OpenAI Codex Security), Rick de Jager, Heewon Song, Sylvie Mayer, Aleksander Alekseev, and Hillai Ben Sasson for reporting this problem. (CVE-2026-14669)
Fix buffer overrun in regexp match/split functions (Masahiko Sawada) §
If passed invalidly-encoded data, these functions could write past the end of their conversion buffer.
The PostgreSQL Project thanks Francesco Verardi for reporting this problem. (CVE-2026-14664)
Harden the ascii() function against invalid input (Michael Paquier) §
By supplying invalidly-encoded input, this function could be coaxed to read and return a few bytes of data that it shouldn't. In assert-enabled builds, its assertions could be triggered too.
The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-18024)
Fix multirange type handling in pg_restore_attribute_stats() (OpenAI Security Research Team) § §
pg_restore_attribute_stats() treated multirange types just like their underlying range type. This works correctly for the bounds histogram, but it was wrong for all the other statistics kinds.
The PostgreSQL Project thanks Amy Burnett (OpenAI Codex Security) for reporting this problem. (CVE-2026-16238)
Make scalarineqsel() check that a constant it expects to be of type tid actually is (Tom Lane) §
This expectation will hold for all the built-in operators that use this estimator, but a maliciously-constructed operator could violate it, leading to a crash or server memory disclosure.
The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14668)
Harden tsvector and tsquery code against overly long values (both individual lexemes and total vector/query length) (Tom Lane) § §
The documented limits were not enforced in all code paths.
The PostgreSQL Project thanks Yuhang Wu, Zhenpeng Lin, Zheng Yu, and Hcamael for reporting these problems. (CVE-2026-14662)
Fix various places that mistakenly assumed they would not have to deal with more than FUNC_MAX_ARGS function arguments (Tom Lane) § §
Notably, the server's actual limit on the number of arguments to an aggregate function is FUNC_MAX_ARGS - 1, but the parser failed to enforce that, creating hazards downstream.
The PostgreSQL Project thanks Zheng Yu, ylwangtju, and Masahiko Sawada for reporting these problems. (CVE-2026-14679)
Reject calls from SQL to functions that take or return type internal (Tom Lane) § §
The existing defenses against doing this have been shown to be insufficient, so add more explicit checks.
The PostgreSQL Project thanks Amy Burnett (OpenAI Codex Security) for reporting this problem. (CVE-2026-14680)
Preserve the ownership of extended statistics objects when they are rebuilt by ALTER TABLE (Masahiko Sawada) §
Previously, the role running ALTER TABLE gained ownership of such objects, but that seems inappropriate.
The PostgreSQL Project thanks Noah Misch for reporting this problem. (CVE-2026-6469)
When deparsing an EXTRACT() function call, quote the field name if needed (Nathan Bossart) §
The parser accepts any string literal as a field name in EXTRACT(), deferring validation to execution. If the call is stored and deparsed (for example during pg_dump), the string body was regurgitated verbatim, allowing SQL injection.
The PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-15741)
Check for USAGE privilege on data types in places that formerly failed to check that (Nathan Bossart) § § §
CREATE TYPE AS RANGE did not check, nor did ALTER TABLE OF, nor did commands that create stored expressions. These omissions allowed roles without USAGE privilege to nonetheless create objects depending on the type, possibly blocking the type's owner from changing the type later.
The PostgreSQL Project thanks Jingzhou Fu for reporting this problem. (CVE-2026-6470)
Invalidate role-dependent cached plans after role changes (Ilya Staroverov, Shinya Kato, Nathan Bossart) §
Role membership, role attribute, and database ownership changes may impact the expected behavior of row-level security policies, but previously we'd continue to use cached plans that were made according to the old state of affairs.
The PostgreSQL Project thanks Ilya Staroverov and Shinya Kato for reporting this problem. (CVE-2026-14666)
Reject GSSEncRequest after direct SSL connection (Michael Paquier) §
After establishing a TLS-encrypted connection, the server would still accept a request for GSSAPI encryption. If that succeeded, the connection would proceed using TLS encryption, but it would look like a GSS connection to the pg_hba rules. Thus, a pg_hba policy intending to disallow TLS would not be enforced correctly.
The PostgreSQL Project thanks p4p3r for reporting this problem. (CVE-2026-14681)
Make mock SCRAM authentication secrets more plausible (Nathan Bossart) §
If a SCRAM login is attempted against a role that doesn't exist or doesn't have a SCRAM secret, we generate a mock secret and carry out the authentication handshake anyway, to avoid revealing these facts to an attacker. But the mock secret was made with a fixed iteration count, which in itself can be an observable response discrepancy. Use the configuration setting scram_iterations instead, to make the mock secret look more like the installation's real secrets.
The PostgreSQL Project thanks Radim Marek for reporting this problem. (CVE-2026-14672)
Fix out-of-bounds writes in ecpg applications caused by invalid bytea data received from the server (Michael Paquier) §
ecpg assumed without checking that any bytea value must begin with \x. A broken or malicious server might send a string shorter than 2 bytes, resulting in memory clobber in the application.
The PostgreSQL Project thanks ylwangtju for reporting this problem. (CVE-2026-16241)
Do not do backquote expansion on the argument of psql's \unrestrict command (Nathan Bossart) §
This oversight in the fix for CVE-2025-8714 allows a malicious server to inject shell commands into plain-text dump output that will be run at restore time on the machine running psql, the exact scenario that CVE-2025-8714 intended to prevent.
The PostgreSQL Project thanks Lucas Velgus, Filip Janus, and Daniel Bakker for reporting this problem. (CVE-2026-18408)
Remove pg_dump's assumption that pg_proc.protrftypes cannot have more than FUNC_MAX_ARGS entries (Tom Lane) §
Since there could be entries for both input and output arguments, it's feasible for this array's length to exceed FUNC_MAX_ARGS (which constrains only input arguments). Even if that were not so, pg_dump cannot assume that the server was built with the same value of FUNC_MAX_ARGS that it has. An overrun would lead to a memory clobber inside pg_dump.
The PostgreSQL Project thanks Masahiko Sawada for reporting this problem. (CVE-2026-19385)
Harden PL/Perl against “tied” Perl arrays and hashes (Tom Lane) §
A tied object that doesn't behave like a regular one could lead to memory overwrite, or to constructing a corrupt result array (which would likely cause problems later).
The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14670)
Fix integer overflows in memory-allocation calculations in PL/Perl and PL/Tcl (Heikki Linnakangas) §
This is the same type of problem as CVE-2026-6473, just in a different part of the code, and is fixed in the same way.
The PostgreSQL Project thanks the Tulya Project (Team Dhiutsa, Bitecope Technologies Private Ltd) for reporting this problem. (CVE-2026-14677)
Ensure that contrib/amcheck functions restrict search_path before executing index expressions (Noah Misch) §
Because amcheck will run such index expressions as the owner of their tables, a caller could potentially hijack search_path-dependent functions to run arbitrary code as the table owner. By default this is not a vulnerability because only superusers are allowed to call amcheck functions; but if that privilege was granted out, it created a larger hazard than the documentation suggests.
The PostgreSQL Project thanks Yuelin Wang and Jacob Brazeal for reporting this problem. (CVE-2026-14673)
Fix integer overflows in contrib/fuzzystrmatch's levenshtein() and levenshtein_less_equal() functions (Nathan Bossart) §
Passing large cost values to these functions could cause integer overflows, thereby producing nonsensical results, and even causing out-of-bounds writes in some cases.
The PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-15742)
Fix buffer overrun in contrib/pg_stat_statements (Álvaro Herrera) §
Query normalization didn't accurately account for the amount of space the normalized string would require.
The PostgreSQL Project thanks Sajeeb Lohani (with TrendAI Zero Day Initiative) and Yuelin Wang for reporting this problem. (CVE-2026-14676)
Fix datatype error in contrib/pg_trgm's GiST picksplit function (Heikki Linnakangas) §
This mistake resulted in reading past the end of the buffer, typically causing bad split decisions; but a crash could ensue if you're very unlucky.
The PostgreSQL Project thanks Mehmet D. Ince for reporting this problem. (CVE-2026-14678)
Remove the plan cache in contrib/refint (Ayush Tiwari) §
This caching behavior has several serious bugs, notably that check_foreign_key() embeds the new key values in its cascade-UPDATE queries, so a cached plan reuses the originally-needed values rather than the key values that should be used. The simplest solution is to remove it.
The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14671)
Ensure that parallel GIN index builds update the table's pg_class.reltuples value correctly (Jan Nidzwetzki, Tomas Vondra) §
A parallel worker could report an uninitialized value for the number of rows it processed, leading to a bogus value for reltuples, even Infinity or NaN. Such values could lead to subsequent autovacuum and autoanalyze operations never deciding that the table needs to be processed. If so, the situation will not self-heal. A manual ANALYZE command, or creation of another index, will be needed to reset reltuples to the correct value. If you have any tables with GIN indexes, it's recommended to check to see if their reltuples entries look sane. A query such as this may be helpful:
SELECT DISTINCT t.oid::regclass, t.reltuples FROM pg_class t JOIN pg_index i ON t.oid = i.indrelid JOIN pg_class ic ON i.indexrelid = ic.oid WHERE t.relhasindex AND ic.relam = 2742;
Fix mis-handling of asynchronous reads when rescanning an asynchronous Append plan node (Alexander Korotkov, Gleb Kashkin, Etsuro Fujita) §
When an upper plan node rescans an Append before having read the entire Append output, we need to discard any in-flight requests sent to external servers (by postgres_fdw for example). This was not done correctly in cases where a subplan has parameter changes or is discarded by partition pruning in the next scan. The outcome could be incorrect query results, an infinite loop, or an assertion failure.
Fix error in partition pruning for RANGE-partitioned tables (David Rowley) §
In some cases the DEFAULT partition would be skipped when it should not be, which could lead to rows missing from query results.
Correctly update foreign-data-wrapper state in a ModifyTable plan node after pruning result relations (Ayush Tiwari, Rafia Sabih) § §
Previously, if run-time partition pruning determined that some partitions of a partitioned target table need not be scanned and the table had any foreign-table partitions, a crash or erroneous behavior was likely.
Fix missed concurrent update in UPDATE with RETURNING OLD on a table that has a BEFORE UPDATE trigger (Dean Rasheed) §
If the target row was concurrently updated, then at isolation level READ COMMITTED any OLD values in RETURNING should reflect the updated row. But stale values were returned if there was a trigger (although the trigger itself, and the final output row, saw the correct values).
Fix hash join performance issue when there are multiple join keys and many NULL values (David Rowley) §
Null-keyed tuples should not get inserted into the hash table, since they will never match any other tuples. The code got this wrong if the null was in a non-last join column, bloating the hash table quite a lot if many inputs contain nulls.
Fix parsing of parenthesized OLD/NEW in RETURNING expressions (Marko Grujic) §
Expressions such as (old).colname and (old).* were mis-handled, effectively converting them to NEW references.
Fix planner's nullability and strictness checks for value IN (array)
These checks should only succeed if the array operand is known to be non-empty, but that consideration was missed, allowing optimizations to be applied that should not be. This could result in wrong query answers if the array actually was empty.
Fix incorrect join removal logic (Matheus Alcantara, Richard Guo) § §
In edge cases, it was possible for a constant output value coming from within the nullable side of an outer join to not be replaced by NULL when it should be.
Clean up PlaceHolderVars more thoroughly during join removal (Richard Guo, Arne Roland) § §
This fix corrects various edge cases that could trip assertions or result in incorrect plans.
Add missed checks for hashability of equality comparisons on container datatypes (arrays, composites, ranges) (Andrei Lepikhov, Tom Lane) §
The planner must verify hashability of the container's component type(s) before deciding it can use a hash-based plan type. This step was missed in some places, leading to “could not identify a hash function” failures at execution.
Avoid pushing WHERE clauses down past a grouping step that has a different equivalence rule (Richard Guo) §
A test on a grouping column that is grouped by a nondeterministic collation is safe to push down only if it is a comparison using that same collation. Otherwise it might filter some rows the grouping would have merged.
Fix mis-optimization of COUNT window functions that have an EXCLUDE clause or lack ORDER BY (Chengpeng Yan, David Rowley) §
These window functions were treated as monotonic when they should not be, allowing wrong answers to be computed.
Avoid “cache lookup failed for collation 0” error when planner looks up statistics for a column of type "char" (Feng Wu) §
Fix ALTER COLUMN ... DROP EXPRESSION to work when there are multiple levels of partitions (Alberto Piai) §
Fix attaching partitions of indexes that are exclusion constraints (Japin Li) §
Notably, this oversight broke dump/restore of partitioned exclusion constraints.
Prevent setting NO INHERIT on partitioned NOT NULL constraints via ALTER CONSTRAINT (Andreas Karlsson) §
NOT NULL constraints on partitioned tables are supposed to be inherited by all partitions, and therefore must not be marked NO INHERIT. This rule was correctly enforced by constraint creation, but not by ALTER TABLE ... ALTER CONSTRAINT.
Disallow renaming a rule to _RETURN (Tom Lane) §
That name is reserved for a view's ON SELECT rule, but ALTER RULE allowed renaming other rules to _RETURN, causing trouble later.
Fix missing lock release for role membership grants in DROP OWNED BY (Jeff Davis) §
This oversight resulted in a warning message, followed by retaining a lock on the membership grant until the end of the transaction.
Fix failure of EXPLAIN when deparsing SQL/JSON aggregates (Richard Guo) §
Some plan structures resulted in “invalid JsonConstructorExpr underlying node type” errors.
Fix use of REINDEX CONCURRENTLY with a deferred uniqueness constraint (Nitin Motiani) §
The transient index copy created during REINDEX CONCURRENTLY was incorrectly marked as enforcing immediate uniqueness, causing spurious reports of constraint violation.
Fix LIKE matching with nondeterministic collations and backslashes (Nitin Motiani, Tom Lane) § §
When using a nondeterministic collation, LIKE mishandled an escaped backslash (\\), treating it as effectively not there. It also did the wrong thing with a leading backslash preceding an ordinary character; in that case the backslash should be effectively ignored, but it caused the ordinary character to be matched exactly rather than allowing the nondeterministic collation to decide if there's a match.
Fix LIKE/regex optimization for indexscan with exact-match pattern (Jelte Fennema-Nio) §
Refactoring for LIKE with non-deterministic collations accidentally broke the optimization for converting a LIKE or regex exact-match pattern to an equality index condition when the index collation doesn't match the expression collation. Among other things, that made psql's \d command much slower.tablename
Fix matching of localized month/day names in to_date() (Heikki Linnakangas) § §
The matching logic misbehaved in cases where case-folding changes the byte length of the string.
Correct case-folding rules for Greek final sigma (Jeff Davis) §
If the string is preceded only by Case Ignorable characters, don't consider it to be a final sigma. This only affects the built-in pg_unicode_fast locale.
Fix incorrect NFC recomposition for Hangul U+11A7 (TBASE) (Diego Frias, Michael Paquier) §
This character was treated as a valid T syllable, which it is not, and hence silently swallowed during normalization.
Avoid possible truncation of output lexemes in case-insensitive synonym dictionaries (Jeff Davis) §
If folding to lower case increased the byte length of a lexeme, it was incorrectly truncated to its original byte length when emitted.
Defend against truncated UTF-8 characters in case-conversion logic (Jeff Davis) §
Fix typo in hash_record_extended() (Man Zeng) §
The code failed to initialize the second isnull argument passed to FunctionCallInvoke(). This is harmless for existing in-core extended hash support functions, which will not examine that value. However, extension-provided hash functions could be affected if they inspect PG_ARGISNULL(1).
Fix pg_get_publication_tables() to not fail if a publishable table is dropped concurrently (Bharath Rupireddy) §
Prevent satisfies_hash_partition() from crashing with VARIADIC NULL (Robert Haas) §
Report invalid-weight errors more cleanly and consistently in tsvector_filter() and allied functions (Ewan Young) §
In particular, report weight characters that are not printable ASCII in octal form (\), as nnncharout() would render them. This avoids possibly producing an invalidly-encoded error message.
Reject out-of-range timestamp shift values in uuidv7() (Baji Shaik) §
The shift value must not be so large as to produce a timestamp out of the range that a v7 UUID can represent. Previously, a garbage UUID value was produced.
Fix mishandling of namespace nodes in xpath() (Michael Paquier) § §
This fix avoids an unexpected “could not copy node” error.
Fix jsonpath's .decimal method to not throw a hard error for incorrect precision or scale (Ewan Young) § §
Silent mode should suppress these errors, but failed to.
Fix NULL-pointer crash when IS JSON or similar constructs have an argument that is of string category but lacks a cast to type text (Ayush Tiwari) §
There are no such data types in core PostgreSQL, but the problem is reachable with some extension types.
Ensure that SQL/JSON ON EMPTY / ON ERROR DEFAULT values are coerced to the correct typmod (Ewan Young) §
For example, the declared precision and scale of a numeric target column were not applied to the default value.
Avoid machine-dependent behavior when dividing the smallest possible money value by -1 (Andrey Rachitskiy) §
Fix crash after out-of-memory failure partway through creation of a cache entry for a text search dictionary (Tom Lane) §
Fix memory-safety bugs in processing of incorrect ispell/hunspell dictionary files (Andrey Rachitskiy) §
Prevent access to other sessions' temporary tables (Jim Jones, Daniil Davydov, Alexander Korotkov) § §
Some code paths failed to prevent this, leading to silently wrong (inconsistent) results.
Prevent “no empty local buffer available” errors during temporary table access (Melanie Plageman) §
Limit the number of local buffers that the read streaming mechanism is allowed to use. Previously, a large value of effective_io_concurrency could allow a single stream to use all the buffers, resulting in failure.
Fix the order in which autovacuum processes databases (Rustam Khamidullin) §
It was unintentionally processing databases from lowest to highest score, when it should be doing the reverse.
Restore full use of shared buffer pool in VACUUM's wraparound failsafe mode (Melanie Plageman) § §
An ordinary VACUUM is limited to use just a few shared buffers, so as not to impinge too much on other processing. However, in failsafe mode we want to reclaim transaction IDs as quickly as possible, so that limit is supposed to be abandoned to allow vacuuming to proceed as fast as possible. This behavior was accidentally broken during refactoring in v18; restore it.
Fix memory leak in parallel vacuum worker processes (Baji Shaik) §
Progress reports from a parallel worker leaked about 1kB per report, with the waste accumulating for the life of the worker process.
Honor query cancel and vacuum delay during GIN index posting-tree cleanup (Paul Kim, Alexander Korotkov) §
The posting tree for a common value can be large, so that this missed check could allow vacuum to run for a long time before noticing an interrupt.
Fix possible mis-decoding of index tuples during GiST and SP-GiST index-only scans (Peter Geoghegan) §
This error could lead to emitting corrupted data from an index-only scan plan. The only affected core opclass is GiST's range_ops, and it could only fail if the range column were not the first index column.
Ensure that the new last block of a bulk-extended table is added to its free space map promptly (Jingtang Zhang) §
An off-by-one error caused the last block of a multi-block table extension to not be marked as free in the map. This would eventually get corrected by vacuum, but meanwhile the space wouldn't be used.
Avoid possible double-free or infinite error recovery loop in resource cleanup during transaction abort (Tom Lane) §
When creating directories, tolerate concurrent creation of the same directory (Andrew Dunstan, Tom Lane) §
Fix JIT-compiled tuple deconstruction code to account correctly for virtual generated columns (David Rowley) §
Prevent creation of dangling object dependencies by acquiring a shared lock on any object being depended on (Bertrand Drouvot) § §
The shared lock will conflict with any attempt to drop the depended-on object, eliminating the race condition that formerly existed. For example, if one session drops a schema (that appears empty to it) concurrently with some other session creating a function in that schema, previously both transactions could commit, leaving an invalid function definition behind. Now, one transaction or the other will fail.
Fix race condition in conflict detection for SERIALIZABLE isolation mode (Peter Geoghegan) §
A conflict could be missed when examining an initially-empty btree index, allowing failure of serializability due to improperly allowing conflicting transactions to commit.
Fix race condition in ProcSignalBarrier code (Masahiko Sawada) §
This error could result in processes getting stuck, typically after reporting “still waiting for backend with PID nnnn to accept ProcSignalBarrier”.
Fix race conditions when a set of processes that belong to the same lock group exit at the same time (Vlad Lesin) § §
These errors could lead to PANIC aborts, with messages such as “latch already owned”. The issue does not normally arise in regular parallel query, since the leader won't exit before seeing its workers finish; but some extensions reach the problem.
Fix WAL logging of operations that clear bits in tables' visibility maps (Melanie Plageman, Andres Freund) § § §
Such VM changes were missed by the WAL summarizer, potentially leading to incorrect incremental backups. We also failed to log full-page images of such VM pages when needed, potentially allowing torn page writes to go uncorrected. This could lead to misbehavior later, such as wrong results from index-only scans.
Prevent WAL summarizer process from getting stuck at a timeline switch (Robert Haas) § §
Fix race with timeline selection in logical decoding during standby promotion (Bertrand Drouvot) § §
Logical decoding being performed on the standby could fail with a “requested WAL segment has already been removed” error. A repeat attempt would succeed, so there was no permanent problem but there was an availability hazard.
Avoid exposing a WAL receiver's full connection string during timeline jumps (Chao Li) §
The pg_stat_wal_receiver view should show a sanitized version of the connection string, without sensitive data. But it transiently showed the full string when we re-use an existing WAL receiver.
Use run-time checks, not just Asserts, to verify the correct number of columns in tuples received during logical replication (Varik Matevosyan) §
A malicious or buggy publisher could send inconsistent numbers of columns. While we could not find a scenario in which this would have serious ill effects, extra caution seems warranted.
Clean up quoting of string parameters within constructed replication commands (Tom Lane) §
Various places that generate replication commands were not being adequately careful about quoting replication slot names and other parameters that need to be inserted into those commands. This could result in unexpected syntax errors in those commands. In principle, a crafted replication slot name could result in SQL injection; but such a scenario seems very unlikely to occur in practice, since replication operations can only be invoked by highly-privileged users and there is no reason for them to use a slot name coming from an untrustworthy source.
Fix logical decoding of empty prepared transactions (Masahiko Sawada) §
A prepared transaction that did not cause any decodable updates could result in sending COMMIT/ROLLBACK PREPARED to the output plugin with no preceding PREPARE. For the built-in subscriber this breaks replication, and other plugins will probably not like it either.
Fix corruption of unlogged sequences after standby promotion (Fujii Masao) §
Previously, if an unlogged sequence was created on the primary and replicated to a standby, accessing the sequence after promoting the standby could fail with “bad magic number in sequence” or related errors.
Fix cascading standby reconnect failure after archive fallback (Marco Nenciarini) §
A cascading standby could fail to reconnect to its upstream standby with “requested starting point ... is ahead of the WAL flush position” after falling back to archive recovery.
Prevent accepting hot-standby connections before WAL replay has reached a consistent database state (Nikhil Sontakke) §
Do not try to clear pg_database.dathasloginevt locally on a standby server (Ayush Tiwari) §
Event trigger cleanup tried to perform that action on standby servers as well as the primary. That can't work on a standby, and there's no need anyway since replay of the primary's database change will soon fix it.
Avoid race condition while dropping obsolete replication slots (Xuneng Zhou) §
An incorrect unlock and log message could occur if another session immediately re-used the dropped slot's shared-memory entry.
Avoid race condition while dropping ephemeral replication slots (Zhijie Hou) §
The slot-releasing code performed some additional updates to the replication slot's shared-memory entry after releasing the slot. This is unsafe since another session could immediately re-use the dropped slot's shared-memory entry. Skip those updates in the case of an ephemeral slot.
Fix stale progress reports during logical replication table synchronization (Shinya Kato) §
Previously, the pg_stat_progress_copy view in the subscriber would continue to show the initial COPY operation as active even after the data copy had finished. The stale entry remained visible until synchronization caught up with the publisher.
Clear base backup progress on backup failure (Chao Li) § §
Previously the pg_stat_progress_basebackup view would continue to show a stale progress entry after a failure, until the replication client disconnected. pg_basebackup normally disconnects immediately, but other clients might not.
Fix possible PANIC due to concurrent drop of pgstats entries when track_functions is enabled (Sami Imseih, Michael Paquier) § § §
Clean up broken local pgstats entry after failing to obtain space for the corresponding shared hashtable entry (Niall Newman) §
Failure to do this led to a null-pointer dereference the next time the local entry was used.
Avoid recording incorrect I/O operation statistics after a failed read or write (Bertrand Drouvot) §
In PL/Perl, avoid NULL pointer dereference crash when working with an invalid PostgreSQL::InServer::ARRAY object (Xing Guo) §
In PL/Python, properly check for errors when working with sequence and mapping objects (Richard Guo) §
Previously, a broken object or an unhandled exception could result in a NULL pointer dereference crash.
In libpq, always drain all pending bytes from the SSL or GSS decryption buffer during pqReadData() (Jacob Champion) § § § §
This avoids edge cases where libpq or its calling application waits for more data to arrive on the socket, but actually all the data has already arrived.
Improve libpq's handling of out-of-memory conditions (Anthonin Bonnefoy) §
Fix libpq's trace facility to print new-style BackendKeyData and CancelRequest messages correctly (Anthonin Bonnefoy) §
Allow libpq to accept ParameterDescription messages exceeding 30000 bytes (Ning Sun) §
Previously, this message type was not among those that libpq's validity heuristics believed could be long. The limit resulted in failure for prepared queries having more than 7498 parameters, which is unlikely but supported.
Fix null-pointer crash in ecpg compiler (Jehan-Guillaume de Rorthais) §
ecpg failed on a DECLARE section containing a union nested inside a struct.
Reject multiple descriptor header items in ecpg's GET/SET DESCRIPTOR statements (Masashi Kamura) §
Previously the grammar allowed this syntax, but broken C code was generated. Adjust the grammar and the documentation to allow only one header item.
Fix issues with deferred errors in pipeline mode in psql (Michael Paquier) §
psql could get stuck or suffer an assertion failure in some scenarios where the server reports an error in response to a Sync message, such as a deferred constraint violation.
Make line widths match in psql's expanded aligned output format (Pavel Stehule) §
When the table's data rows are narrower than the record header lines, widen the data rows to match the headers, avoiding unsightly output.
Enforce the intended upper limit for psql's special variable WATCH_INTERVAL (Sven Klemm, Daniel Gustafsson) §
If a too-large value was given, psql reported an error but applied the setting anyway.
Fix psql's privilege check for showing database size in \l+ (Christoph Berg) §
The underlying server function permits users who have pg_read_all_stats privileges to see the sizes of all databases, even if they lack CONNECT privilege. But psql was unaware of that provision and would not call the function unless the user has CONNECT privilege.
Fix psql's tab completion for \df to consider procedures too (Erik Wienhold) §
Fix thread-safety bug in pgbench (Fujii Masao) §
When pgbench runs with multiple threads and the --verbose-errors option, different threads could attempt to use the same buffer to construct error messages, leading to corrupted log output.
In pg_combinebackup, prevent infinite loop if the source file is shorter than expected (Peter Eisentraut) §
Fix cleanup of publisher-side objects after errors in pg_createsubscriber (Nisha Moond) §
When pg_createsubscriber fails after creating logical replication objects, it should remove the publication and replication slot that it created on the publisher. Some error cases failed to do so.
Use the source cluster's group-read file permissions for pg_recvlogical output files (Fujii Masao) §
pg_recvlogical was documented to behave this way, but it never actually enabled group-read.
Fix inconsistent behavior of pg_restore with --statistics or --statistics-only (Chao Li, Michael Paquier) § §
When combined with other selective-restore options such as --schema, these options failed to restore the expected items, unlike pg_dump with similar options.
Fix vacuumdb --missing-stats-only to ignore partitioned expression indexes (Baji Shaik) §
Previously, vacuumdb would always attempt to ANALYZE the partitioned table, accomplishing nothing since statistics are never created for partitioned indexes, only for their leaf indexes.
In contrib/amcheck, fix failure to report corruption of a btree metapage's allequalimage flag (Chao Li) §
In contrib/amcheck, fix query-lifespan memory leak while verifying a GIN index (Kirill Reshke) §
In contrib/amcheck, handle short-header varlena datums correctly (Andrey Borodin) §
This error could result in doing excess work while verifying a btree index, but seems not to have had any worse consequences.
In contrib/btree_gist, fix NaN handling in the float4 and float8 opclasses (Bill Kim, Tom Lane) §
Comparisons, as well as the GiST penalty and distance functions, did not account for NaN and would give the wrong answer when handed one. It is recommended to reindex btree_gist indexes on float columns after installing this update, if there is any possibility that there are NaN entries in those columns.
In contrib/btree_gist, fix sorting of bit/varbit entries during GiST index construction (Tom Lane) §
Values of bit types were sorted as though they were byteas, which did not cause any obvious failure but would result in an inefficient index, since the types' representations are different. It is recommended to reindex btree_gist indexes on bit columns after installing this update.
In contrib/btree_gist, fix searches using a not-equal operator (Ayush Tiwari) §
For variable-length data types, the code for scanning non-leaf index pages applied the wrong comparison function, leading to wrong results and potentially crashes.
In contrib/dblink and contrib/postgres_fdw, ensure that a user-mapping setting for use_scram_passthrough overrides one for a foreign server (Matheus Alcantara) § §
Previously the precedence went the other way, but that is inconsistent with the behavior of other foreign-table options.
Reject setting use_scram_passthrough on contrib/dblink foreign-data wrappers (Matheus Alcantara) §
This option is only meaningful on foreign servers and user mappings, but dblink incorrectly allowed it at the FDW level as well (and then ignored it).
Fix unguarded recursion and loops in contrib/hstore_plperl, contrib/jsonb_plperl, and contrib/jsonb_plpython (Aleksander Alekseev) § §
Prevent stack overflow when dealing with deeply nested jsonb values, and allow interruption of the infinite loop caused when attempting to dereference circular chains of Perl object references.
Fix missed release of statistics catcache entry in contrib/intarray (Man Zeng) §
This oversight led to warnings like “resource was not closed: cache pg_statistic”.
In contrib/ltree, fix integer overflow in comparisons (Ayush Tiwari) §
ltree values containing more than about 14,653 labels resulted in wrong comparison answers due to overflow. If a btree index contains such values, it is probably corrupt and should be reindexed after installing this update.
In contrib/pgcrypto, avoid double-free crash after encountering an error while using an OSSLCipher object (Yuelin Wang) §
Fix out-of-bounds access in contrib/pg_prewarm's autoprewarm worker (Matheus Alcantara) §
The code tried to fetch a value from one past the end of an array, risking a segfault.
Fix array overrun in contrib/pg_surgery's heap_force_kill and heap_force_freeze functions (Michael Paquier) §
Attempting to change a TID whose offset number equals MaxHeapTuplesPerPage wrote one byte past the end of the allocated array, potentially crashing the server.
In contrib/pg_surgery, avoid infinite loop with TID arrays having more than 64K elements (Andrey Rachitskiy) §
Avoid NULL-pointer dereference in contrib/refint's check_foreign_key() (Ayush Tiwari) §
In the on-update-cascade case, a null value of a referenced column led to a crash. This is an oversight in the fix for CVE-2026-6637, but the code that was there before that wasn't really right either.
Fix contrib/seg to print segments with ~ certainty indicators correctly (Ewan Young) §
Due to a typo, seg_out() did not print a ~ certainty indicator attached to a segment's upper boundary. Worse, if the lower boundary had ~ while the upper boundary had no indicator, the upper boundary was not printed at all, incorrectly converting the value into an open interval.
Fix crash with namespace nodes in contrib/xml2's xpath_nodeset() function (Andrey Chernyy, Michael Paquier) §
Support building PostgreSQL with OpenSSL 4 (Daniel Gustafsson) §
Update time zone data files to tzdata release 2026c (Tom Lane) §
Alberta (America/Edmonton) will be on year-round UTC-06 (effectively, permanent DST) beginning in November 2026. This release assumes that their TZ abbreviation will be CST from that time forward. That seems likely to change, but it's unclear what new abbreviation will be used.
Morocco (Africa/Casablanca) will move to permanent UTC+00, without daylight saving time transitions, on 2026-09-20.