Release notes for prior release branches can be found at https://www.postgresql.org/docs/release/

Release date: 2023-02-09

This release contains a variety of fixes from 15.1. For information about new features in major release 15, see Section E.3.

E.1.1. Migration to Version 15.2

A dump/restore is not required for those running 15.X.

However, if you are upgrading from a version earlier than 15.1, see Section E.2.

E.1.2. Changes

• libpq can leak memory contents after GSSAPI transport encryption initiation fails (Jacob Champion)

  A modified server, or an unauthenticated man-in-the-middle, can send a not-zero-terminated error message during setup of GSSAPI (Kerberos) transport encryption. libpq will then copy that string, as well as following bytes in application memory up to the next zero byte, to its error report. Depending on what the calling application does with the error report, this could result in disclosure of application memory contents. There is also a small probability of a crash due to reading beyond the end of memory. Fix by properly zero-terminating the server message. (CVE-2022-41862)

• Fix calculation of which GENERATED columns need to be updated in child tables during an UPDATE on a partitioned table or inheritance tree (Amit Langote, Tom Lane)

  This fixes failure to update GENERATED columns that do not exist in the parent table, or that have different dependencies than are in the parent column's generation expression.

• Fix possible failure of MERGE to compute GENERATED columns (Dean Rasheed)

  When the first row-level action of the MERGE was an UPDATE, any subsequent INSERT actions would fail to compute GENERATED columns that were deemed unnecessary to compute for the UPDATE action (due to not depending on any of the UPDATE target columns).

• Fix MERGE's check for unreachable WHEN clauses (Dean Rasheed)

  A WHEN clause following an unconditional WHEN clause should be rejected as unreachable, but this case was not always detected.

• Fix MERGE's rule-detection test (Dean Rasheed)

  MERGE is not supported on tables with rules; but it also failed on tables that once had rules but no longer do.

• In MERGE, don't count a DO NOTHING action as a processed tuple (Álvaro Herrera)

  This makes the code's behavior match the documentation.

• Allow a WITH RECURSIVE ... CYCLE CTE to access its output column (Tom Lane)

  A reference to the SET column from within the CTE would fail with “cache lookup failed for type 0”.

• Fix handling of pending inserts when doing a bulk insertion to a foreign table (Etsuro Fujita)

  In some cases pending insertions were not flushed to the FDW soon enough, leading to logical inconsistencies, for example BEFORE ROW triggers not seeing rows they should be able to see.

• Allow REPLICA IDENTITY to be set on an index that's not (yet) valid (Tom Lane)

  When pg_dump dumps a partitioned index that's marked REPLICA IDENTITY, it generates a command sequence that applies REPLICA IDENTITY before the partitioned index has been marked valid, causing restore to fail. There seems no very good reason to prohibit doing it in that order, so allow it. The marking will have no effect anyway until the index becomes valid.

• Fix handling of DEFAULT markers in rules that perform an INSERT from a multi-row VALUES list (Dean Rasheed)

  In some cases a DEFAULT marker would not get replaced with the proper default-value expression, leading to an “unrecognized node type” error.

• Reject uses of undefined variables in jsonpath existence checks (Alexander Korotkov, David G. Johnston)

  While jsonpath match operators threw an error for an undefined variable in the path pattern, the existence operators silently treated it as a match.

• Fix jsonb subscripting to cope with toasted subscript values (Tom Lane, David G. Johnston)

  Using a text value fetched directly from a table as a jsonb subscript was likely to fail. Fetches would usually not find any matching element. Assignments could store the value with a garbage key, although keys long enough to cause that problem are probably rare in the field.

• Fix edge-case data corruption in parallel hash joins (Dmitry Astapov)

  If the final chunk of a large tuple being written out to a temporary file was exactly 32760 bytes, it would be corrupted due to a fencepost bug. The query would typically fail later with corrupted-data symptoms.

• Honor non-default settings of checkpoint_completion_target (Bharath Rupireddy)

  Internal state was not updated after a change in checkpoint_completion_target, possibly resulting in performing checkpoint I/O faster or slower than desired, especially if that setting was changed on-the-fly.

• Log the correct ending timestamp in recovery_target_xid mode (Tom Lane)

  When ending recovery based on the recovery_target_xid setting with recovery_target_inclusive = off, we printed an incorrect timestamp (always 2000-01-01) in the “recovery stopping before ... transaction” log message.

• Improve error reporting for some buffered file read failures (Peter Eisentraut)

  Correctly report a short read, giving the numbers of bytes desired and actually read, instead of reporting an irrelevant error code. Most places got this right already, but some recently-written replication logic did not.

• Remove arbitrary limit on number of elements in int2vector and oidvector (Tom Lane)

  The input functions for these types previously rejected more than 100 elements. With the introduction of the logical replication column list feature, it's necessary to accept int2vectors having up to 1600 columns, otherwise long column lists cause logical-replication failures.

• In extended query protocol, avoid an immediate commit after ANALYZE if we're running a pipeline (Tom Lane)

  If there's not been an explicit BEGIN TRANSACTION, ANALYZE would take it on itself to commit, which should not happen within a pipelined series of commands.

• Reject cancel request packets having the wrong length (Andrey Borodin)

  The server would process a cancel request even if its length word was too small. This led to reading beyond the end of the allocated buffer. In theory that could cause a segfault, but it seems quite unlikely to happen in practice, since the buffer would have to be very close to the end of memory. The more likely outcome was a bogus log message about wrong backend PID or cancel code. Complain about the wrong length, instead.

• Fix planner preprocessing oversights for window function run-condition expressions (Richard Guo, David Rowley)

  This could lead to planner errors such as “WindowFunc not found in subplan target lists”.

• Fix possible dangling-pointer access during execution of window function run-condition expressions (David Rowley)

  In practice, because the run-condition optimization is only applied to certain window functions that happen to all return int8, this only manifested as a problem on 32-bit builds.

• Add recursion and looping defenses in subquery pullup (Tom Lane)

  A contrived query can result in deep recursion and unreasonable amounts of time spent trying to flatten subqueries. A proper fix for that seems unduly invasive for a back-patch, but we can at least add stack depth checks and an interrupt check to allow the query to be cancelled.

• Fix planner issues when combining Memoize nodes with partitionwise joins or parameterized nestloops (Richard Guo)

  These errors could lead to not using Memoize in contexts where it would be useful, or possibly to wrong query plans.

• Fix partitionwise-join code to tolerate failure to produce a plan for each partition (Tom Lane)

  This could result in “could not devise a query plan for the given query” errors.

• Limit the amount of cleanup work done by get_actual_variable_range (Simon Riggs)

  Planner runs occurring just after deletion of a large number of tuples appearing at the end of an index could expend significant amounts of work setting the “killed” bits for those index entries. Limit the amount of work done in any one query by giving up on this process after examining 100 heap pages. All the cleanup will still happen eventually, but without so large a performance hiccup.

• Prevent the statistics machinery from getting confused when a relation's relkind changes (Andres Freund)

  Converting a table to a view could lead to crashes or assertion failures.

• Fix under-parenthesized display of AT TIME ZONE constructs (Tom Lane)

  This could result in dump/restore failures for rules or views in which an argument of AT TIME ZONE is itself an expression.

• Prevent clobbering of cached parsetrees for utility statements in SQL functions (Tom Lane, Daniel Gustafsson)

  If a SQL-language function executes the same utility command more than once within a single calling query, it could crash or report strange errors such as “unrecognized node type”.

• Ensure that execution of full-text-search queries can be cancelled while they are performing phrase matches (Tom Lane)

• Fix memory leak in hashing strings with nondeterministic collations (Jeff Davis)

• Fix deadlock between DROP DATABASE and logical replication worker process (Hou Zhijie)

  This was caused by an ill-advised choice to block interrupts while creating a logical replication slot in the worker. In version 15 that could lead to an undetected deadlock. In version 14, no deadlock has been observed, but it's still a bad idea to block interrupts while waiting for network I/O.

• Clean up the libpq connection object after a failed replication connection attempt (Andres Freund)

  The previous coding leaked the connection object. In background code paths that's pretty harmless because the calling process will give up and exit. But in commands such as CREATE SUBSCRIPTION, such a failure resulted in a small session-lifespan memory leak.

• In hot-standby servers, reduce processing effort for tracking XIDs known to be active on the primary (Simon Riggs, Michail Nikolaev)

  Insufficiently-aggressive cleanup of the KnownAssignedXids array could lead to poor performance, particularly when max_connections is set to a large value on the standby.

• Ignore invalidated logical-replication slots while determining oldest catalog xmin (Sirisha Chamarthi)

  A replication slot could prevent cleanup of dead tuples in the system catalogs even after it becomes invalidated due to exceeding max_slot_wal_keep_size. Thus, failure of a replication consumer could lead to indefinitely-large catalog bloat.

• In logical decoding, notify the remote node when a transaction is detected to have crashed (Hou Zhijie)

  After a server restart, we'll re-stream the changes for transactions occurring shortly before the restart. Some of these transactions probably never completed; when we realize that one didn't we throw away the relevant decoding state locally, but we neglected to tell the subscriber about it. That led to the subscriber keeping useless streaming files until it's next restarted.

• Fix uninitialized-memory usage in logical decoding (Masahiko Sawada)

  In certain cases, resumption of logical decoding could try to re-use XID data that had already been freed, leading to unpredictable behavior.

• Acquire spinlock while updating shared state during logical decoding context creation (Masahiko Sawada)

  We neglected to acquire the appropriate lock while updating data about two-phase transactions, potentially allowing other processes to see inconsistent data.

• Fix pgoutput replication plug-in to not send columns not listed in a table's replication column list (Hou Zhijie)

  UPDATE and DELETE events did not pay attention to the configured column list, thus sending more data than expected. This did not cause a problem when the receiver is our built-in logical replication code, but it might confuse other receivers, and in any case it wasted network bandwidth.

• Avoid rare “failed to acquire cleanup lock” panic during WAL replay of hash-index page split operations (Robert Haas)

• Advance a heap page's LSN when setting its all-visible bit during WAL replay (Jeff Davis)

  Failure to do this left the page possibly different on standby servers than the primary, and violated some other expectations about when the LSN changes. This seems only a theoretical hazard so far as PostgreSQL itself is concerned, but it could upset third-party tools.

• Fix int64_div_fast_to_numeric() to work for a wider range of inputs (Dean Rasheed)

  This function misbehaved with some values of its second argument. No such usages exist in core PostgreSQL, but it's clearly a hazard for external modules, so repair.

• Fix latent buffer-overrun problem in WaitEventSet logic (Thomas Munro)

  The epoll-based and kqueue-based implementations could ask the kernel for too many events if the size of their internal buffer was different from the size of the caller's output buffer. That case is not known to occur in released PostgreSQL versions, but this error is a hazard for external modules and future bug fixes.

• Avoid nominally-undefined behavior when accessing shared memory in 32-bit builds (Andres Freund)

  clang's undefined-behavior sanitizer complained about use of a pointer that was less aligned than it should be. It's very unlikely that this would cause a problem in non-debug builds, but it's worth fixing for testing purposes.

• Fix assertion failure in BRIN minmax-multi opclasses (Tomas Vondra)

  The assertion was overly strict, so this mistake was harmless in non-assert builds.

• Remove faulty assertion in useless-RESULT-RTE optimization logic (Tom Lane)

• Fix copy-and-paste errors in cache-lookup-failure messages for ACL checks (Justin Pryzby)

  In principle these errors should never be reached. But if they are, some of them reported the wrong type of object.

• Fix possible corruption of very large tablespace map files in pg_basebackup (Antonin Houska)

• Avoid harmless warning from pg_dump in --if-exists mode (Tom Lane)

  If the public schema has a non-default owner then use of pg_dump's --if-exists option resulted in a warning message “warning: could not find where to insert IF EXISTS in statement "-- *not* dropping schema, since initdb creates it"”. The dump output was okay, though.

• Fix psql's \sf and \ef commands to handle SQL-language functions that have SQL-standard function bodies (Tom Lane)

  These commands misidentified the start of the function body when it used new-style syntax.

• Fix tab completion of ALTER FUNCTION/PROCEDURE/ROUTINE ... SET SCHEMA (Dean Rasheed)

• Update contrib/pageinspect to mark its disk-accessing functions as PARALLEL RESTRICTED (Tom Lane)

  This avoids possible failure if one of these functions is used to examine a temporary table, since a session's temporary tables are not accessible from parallel workers.

• Fix contrib/seg to not crash or print garbage if an input number has more than 127 digits (Tom Lane)

• Fix build on Microsoft Visual Studio 2013 (Tom Lane)

  A previous patch supposed that all platforms of interest have snprintf(), but MSVC 2013 isn't quite there yet. Revert to using sprintf() on that platform.

• Fix compile failure in building PL/Perl with MSVC when using Strawberry Perl (Andrew Dunstan)

• Fix mismatch of PL/Perl built with MSVC versus a Perl library built with gcc (Andrew Dunstan)

  Such combinations could previously fail with “loadable library and perl binaries are mismatched” errors.

• Suppress compiler warnings from Perl's header files (Andres Freund)

  Our preferred compiler options provoke warnings about constructs appearing in recent versions of Perl's header files. When using gcc, we can suppress these warnings with a pragma.

• Fix pg_waldump to build on compilers that don't discard unused static-inline functions (Tom Lane)

• Update time zone data files to tzdata release 2022g for DST law changes in Greenland and Mexico, plus historical corrections for northern Canada, Colombia, and Singapore.

  Notably, a new timezone America/Ciudad_Juarez has been split off from America/Ojinaga.

The release notes contain the significant changes in each PostgreSQL release, with major features and migration issues listed at the top. The release notes do not contain changes that affect only a few users or changes that are internal and therefore not user-visible. For example, the optimizer is improved in almost every release, but the improvements are usually observed by users as simply faster queries.

A complete list of changes for each release can be obtained by viewing the Git logs for each release. The pgsql-committers email list records all source code changes as well. There is also a web interface that shows changes to specific files.

The name appearing next to each item represents the major developer for that item. Of course all changes involve community discussion and patch review, so each item is truly a community effort.

Release date: 2022-11-10

This release contains a variety of fixes from 15.0. For information about new features in major release 15, see .

E.2.1. Migration to Version 15.1

A dump/restore is not required for those running 15.X.

However, if you regularly create and drop tables exceeding 1GB, see the first changelog entry below.

E.2.2. Changes

• Fix failure to remove non-first segments of large tables (Tom Lane)

  PostgreSQL splits large tables into multiple files (normally with 1GB per file). The logic for dropping a table was broken and would miss removing all but the first such file, in two cases: drops of temporary tables and WAL replay of drops of regular tables. Applications that routinely create multi-gigabyte temporary tables could suffer significant disk space leakage.

  Orphaned temporary-table files are removed during postmaster start, so the mere act of updating to 15.1 is sufficient to clear any leaked temporary-table storage. However, if you suffered any database crashes while using 15.0, and there might have been large tables dropped just before such crashes, it's advisable to check the database directories for files named according to the pattern NNNN.NN. If there is no matching file named just NNNN (without the .NN suffix), these files should be removed manually.

• Fix handling of DEFAULT tokens that appear in a multi-row VALUES clause of an INSERT on an updatable view (Tom Lane)

  This oversight could lead to “cache lookup failed for type” errors, or in older branches even to crashes.

• Disallow rules named _RETURN that are not ON SELECT (Tom Lane)

  This avoids confusion between a view's ON SELECT rule and any other rules it may have.

• Avoid failure in EXPLAIN VERBOSE for a query using SEARCH BREADTH FIRST with constant initial values (Tom Lane)

• Prevent use of MERGE on a partitioned table with foreign-table partitions (Álvaro Herrera)

  The case isn't supported, and previously threw an incomprehensible error.

• Fix construction of per-partition foreign key constraints while doing ALTER TABLE ATTACH PARTITION (Jehan-Guillaume de Rorthais, Álvaro Herrera)

  Previously, incorrect or duplicate constraints could be constructed for the newly-added partition.

• Fix planner failure with extended statistics on partitioned or inherited tables (Richard Guo, Justin Pryzby)

  Some cases failed with “cache lookup failed for statistics object”.

• Fix mis-ordering of WAL operations in fast insert path for GIN indexes (Matthias van de Meent, Zhang Mingli)

  This mistake is not known to have any negative consequences within core PostgreSQL, but it did cause issues for some extensions.

• Fix bugs in logical decoding when replay starts from a point between the beginning of a transaction and the beginning of its subtransaction (Masahiko Sawada, Kuroda Hayato)

  These errors could lead to assertion failures in debug builds, and otherwise to memory leaks.

• Accept interrupts in more places during logical decoding (Amit Kapila, Masahiko Sawada)

  This ameliorates problems with slow shutdown of replication workers.

• Prevent attempts to replicate into a foreign-table partition in replication workers (Shi Yu, Tom Lane)

  Although partitioned tables can have foreign tables as partitions, replicating into such a partition isn't currently supported. The logical replication worker process would crash if it was attempted. Now, an error is thrown.

• Avoid crash after function syntax error in replication workers (Maxim Orlov, Anton Melnikov, Masahiko Sawada, Tom Lane)

  If a syntax error occurred in a SQL-language or PL/pgSQL-language CREATE FUNCTION or DO command executed in a logical replication worker, the worker process would crash with a null pointer dereference or assertion failure.

• Avoid double call of the shutdown callback of an archiver module (Nathan Bossart, Bharath Rupireddy)

• Add plan-time check for attempted access to a table that has no table access method (Tom Lane)

  This prevents a crash in some catalog-corruption scenarios, for example use of a view whose ON SELECT rule is missing.

• Prevent postmaster crash when shared-memory state is corrupted (Tom Lane)

  The postmaster process is supposed to survive and initiate a database restart if shared memory becomes corrupted, but one bit of code was being insufficiently cautious about that.

• In libpq, handle single-row mode correctly when pipelining (Denis Laxalde)

  The single-row flag was not reset at the correct time if pipeline mode was also active.

• Fix psql's exit status when a command-line query is canceled (Peter Eisentraut)

  psql -c query would exit successfully if the query was canceled. Fix it to exit with nonzero status, as in other error cases.

• Allow cross-platform tablespace relocation in pg_basebackup (Robert Haas)

  Allow the remote path in --tablespace-mapping to be either a Unix-style or Windows-style absolute path, since the source server could be on a different OS than the local system.

• Fix pg_dump's failure to dump comments attached to some CHECK constraints (Tom Lane)

• Fix CREATE DATABASE to allow its oid parameter to exceed 231 (Tom Lane)

  This oversight prevented pg_upgrade from succeeding when the source installation contained databases with OIDs larger than that.

• In pg_stat_statements, fix access to already-freed memory (zhaoqigui)

  This occurred if pg_stat_statements tracked a ROLLBACK command issued via extended query protocol. In debug builds it consistently led to an assertion failure. In production builds there would often be no visible ill effect; but if the freed memory had already been reused, the likely result would be to store garbage for the query string.

• Fix incompatibilities with LLVM 15 (Thomas Munro, Andres Freund)

• Allow use of __sync_lock_test_and_set() for spinlocks on any machine (Tom Lane)

  This eases porting to new machine architectures, at least if you're using a compiler that supports this GCC builtin function.

• Rename symbol REF to REF_P to avoid compile failure on recent macOS (Tom Lane)

• Avoid using sprintf, to avoid compile-time deprecation warnings (Tom Lane)

• Update time zone data files to tzdata release 2022f for DST law changes in Chile, Fiji, Iran, Jordan, Mexico, Palestine, and Syria, plus historical corrections for Chile, Crimea, Iran, and Mexico.

  Also, the Europe/Kiev zone has been renamed to Europe/Kyiv. Also, the following zones have been merged into nearby, more-populous zones whose clocks have agreed with them since 1970: Antarctica/Vostok, Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik, Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg, Europe/Monaco, Europe/Oslo, Europe/Stockholm, Indian/Christmas, Indian/Cocos, Indian/Kerguelen, Indian/Mahe, Indian/Reunion, Pacific/Chuuk, Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei, Pacific/Wake and Pacific/Wallis. (This indirectly affects zones that were already links to one of these: Arctic/Longyearbyen, Atlantic/Jan_Mayen, Iceland, Pacific/Ponape, Pacific/Truk, and Pacific/Yap.) America/Nipigon, America/Rainy_River, America/Thunder_Bay, Europe/Uzhgorod, and Europe/Zaporozhye were also merged into nearby zones after discovering that their claimed post-1970 differences from those zones seem to have been errors. In all these cases, the previous zone name remains as an alias; but the actual data is that of the zone that was merged into.

  These zone mergers result in loss of pre-1970 timezone history for the merged zones, which may be troublesome for applications expecting consistency of timestamptz display. As an example, the stored value 1944-06-01 12:00 UTC would previously display as 1944-06-01 13:00:00+01 if the Europe/Stockholm zone is selected, but now it will read out as 1944-06-01 14:00:00+02.

  It is possible to build the time zone data files with options that will restore the older zone data, but that choice also inserts a lot of other old (and typically poorly-attested) zone data, resulting in more total changes from the previous release than accepting these upstream changes does. PostgreSQL has chosen to ship the tzdb data as-recommended, and so far as we are aware most major operating system distributions are doing likewise. However, if these changes cause significant problems for your application, a possible solution is to install a local build of the time zone data files using tzdb's backwards-compatibility options (see their PACKRATDATA and PACKRATLIST options).

Release date: 2022-10-13

E.3.1. Overview

PostgreSQL 15 contains many new features and enhancements, including:

• Support for the SQL MERGE command.

• Selective publication of tables' contents within logical replication publications, through the ability to specify column lists and row filter conditions.

• More options for compression, including support for Zstandard (zstd) compression. This includes support for performing compression on the server side during pg_basebackup.

• Support for structured server log output using the JSON format.

• Performance improvements, particularly for in-memory and on-disk sorting.

The above items and other new features of PostgreSQL 15 are explained in more detail in the sections below.

E.3.2. Migration to Version 15

A dump/restore using pg_dumpall or use of pg_upgrade or logical replication is required for those wishing to migrate data from any previous release. See Section 19.6 for general information on migrating to new major releases.

Version 15 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:

• Remove PUBLIC creation permission on the public schema (Noah Misch)

  The new default is one of the secure schema usage patterns that Section 5.9.6 has recommended since the security release for CVE-2018-1058. The change applies to new database clusters and to newly-created databases in existing clusters. Upgrading a cluster or restoring a database dump will preserve public's existing permissions.

  For existing databases, especially those having multiple users, consider revoking CREATE permission on the public schema to adopt this new default. For new databases having no need to defend against insider threats, granting CREATE permission will yield the behavior of prior releases.

• Change the owner of the public schema to be the new pg_database_owner role (Noah Misch)

  This allows each database's owner to have ownership privileges on the public schema within their database. Previously it was owned by the bootstrap superuser, so that non-superuser database owners could not do anything with it.

  This change applies to new database clusters and to newly-created databases in existing clusters. Upgrading a cluster or restoring a database dump will preserve public's existing ownership specification.

• Remove long-deprecated exclusive backup mode (David Steele, Nathan Bossart)

  If the database server stops abruptly while in this mode, the server could fail to start. The non-exclusive backup mode is considered superior for all purposes. Functions pg_start_backup()/pg_stop_backup() have been renamed to pg_backup_start()/pg_backup_stop(), and the functions pg_backup_start_time() and pg_is_in_backup() have been removed.

• Increase hash_mem_multiplier default to 2.0 (Peter Geoghegan)

  This allows query hash operations to use more work_mem memory than other operations.

• Remove server-side language plpython2u and generic Python language plpythonu (Andres Freund)

  Python 2.x is no longer supported. While the original intent of plpythonu was that it could eventually refer to plpython3u, changing it now seems more likely to cause problems than solve them, so it's just been removed.

• Generate an error if array_to_tsvector() is passed an empty-string array element (Jean-Christophe Arnu)

  This is prohibited because lexemes should never be empty. Users of previous Postgres releases should verify that no empty lexemes are stored because they can lead to dump/restore failures and inconsistent results.

• Generate an error when chr() is supplied with a negative argument (Peter Eisentraut)

• Prevent CREATE OR REPLACE VIEW from changing the collation of an output column (Tom Lane)

• Disallow zero-length Unicode identifiers, e.g., U&"" (Peter Eisentraut)

  Non-Unicode zero-length identifiers were already disallowed.

• Prevent numeric literals from having non-numeric trailing characters (Peter Eisentraut)

  Previously, query text like 123abc would be interpreted as 123 followed by a separate token abc.

• Adjust JSON numeric literal processing to match the SQL/JSON-standard (Peter Eisentraut)

  This accepts numeric formats like .1 and 1., and disallows trailing junk after numeric literals, like 1.type().

• When interval input provides a fractional value for a unit greater than months, round to the nearest month (Bruce Momjian)

  For example, convert 1.99 years to 2 years, not 1 year 11 months as before.

• Improve consistency of interval parsing with trailing periods (Tom Lane)

  Numbers with trailing periods were rejected on some platforms.

• Mark the interval output function as stable, not immutable, since it depends on IntervalStyle (Tom Lane)

  This will, for example, cause creation of indexes relying on the text output of interval values to fail.

• Detect integer overflow in interval justification functions (Joe Koshakow)

  The affected functions are justify_interval(), justify_hours(), and justify_days().

• Change the I/O format of type "char" for non-ASCII characters (Tom Lane)

  Bytes with the high bit set are now output as a backslash and three octal digits, to avoid encoding issues.

• Remove the default ADMIN OPTION privilege a login role has on its own role membership (Robert Haas)

  Previously, a login role could add/remove members of its own role, even without ADMIN OPTION privilege.

• Allow logical replication to run as the owner of the subscription (Mark Dilger)

  Because row-level security policies are not checked, only superusers, roles with bypassrls, and table owners can replicate into tables with row-level security policies.

• Prevent UPDATE and DELETE logical replication operations on tables where the subscription owner does not have SELECT permission on the table (Jeff Davis)

  UPDATE and DELETE commands typically involve reading the table as well, so require the subscription owner to have table SELECT permission.

• When EXPLAIN references the session's temporary object schema, refer to it as pg_temp (Amul Sul)

  Previously the actual schema name was reported, leading to inconsistencies across sessions.

• Fix pg_statio_all_tables to sum values for the rare case of TOAST tables with multiple indexes (Andrei Zubkov)

  Previously such cases would show one row for each index.

• Disallow setting custom options that match the name of an installed extension, but are not one of the extension's declared variables (Florin Irion, Tom Lane)

  This change causes any such pre-existing variables to be deleted during extension load, and then prevents new ones from being created later in the session. The intent is to prevent confusion about whether a variable is associated with an extension or not.

• Remove obsolete server variable stats_temp_directory (Andres Freund, Kyotaro Horiguchi)

• Improve the algorithm used to compute random() (Fabien Coelho)

  This will cause random()'s results to differ from what was emitted by prior versions, even for the same seed value.

• libpq's PQsendQuery() function is no longer supported in pipeline mode (Álvaro Herrera)

  Applications that are using that combination will need to be modified to use PQsendQueryParams() instead.

• On non-Windows platforms, consult the HOME environment variable to find the user's home directory (Anders Kaseorg)

  If HOME is empty or unset, fall back to the previous method of checking the <pwd.h> database. This change affects libpq (for example, while looking up ~/.pgpass) as well as various client application programs.

• Remove pg_dump's --no-synchronized-snapshots option (Tom Lane)

  All still-supported server versions support synchronized snapshots, so there's no longer a need for this option.

• After an error is detected in psql's --single-transaction mode, change the final COMMIT command to ROLLBACK only if ON_ERROR_STOP is set (Michael Paquier)

• Avoid unnecessary casting of constants in queries sent by postgres_fdw (Dian Fay)

  When column types are intentionally different between local and remote databases, such casts could cause errors.

• Remove xml2's xml_is_well_formed() function (Tom Lane)

  This function has been implemented in the core backend since Postgres 9.1.

• Allow custom scan providers to indicate if they support projections (Sven Klemm)

  The default is now that custom scan providers are assumed to not support projections; those that do will need to be updated for this release.

E.3.3. Changes

Below you will find a detailed account of the changes between PostgreSQL 15 and the previous major release.

E.3.3.1. Server

• Record and check the collation version of each database (Peter Eisentraut)

  This feature is designed to detect collation version changes to avoid index corruption. Function pg_database_collation_actual_version() reports the underlying operating system collation version, and ALTER DATABASE ... REFRESH sets the recorded database collation version to match the operating system collation version.

• Allow ICU collations to be set as the default for clusters and databases (Peter Eisentraut)

  Previously, only libc-based collations could be selected at the cluster and database levels. ICU collations could only be used via explicit COLLATE clauses.

• Add system view pg_ident_file_mappings to report pg_ident.conf information (Julien Rouhaud)

E.3.3.1.1. Partitioning

• Improve planning time for queries referencing partitioned tables (David Rowley)

  This change helps when only a few of many partitions are relevant.

• Allow ordered scans of partitions to avoid sorting in more cases (David Rowley)

  Previously, a partitioned table with a DEFAULT partition or a LIST partition containing multiple values could not be used for ordered partition scans. Now they can be used if such partitions are pruned during planning.

• Improve foreign key behavior of updates on partitioned tables that move rows between partitions (Amit Langote)

  Previously, such updates ran a delete action on the source partition and an insert action on the target partition. PostgreSQL will now run an update action on the partition root, providing cleaner semantics.

• Allow CLUSTER on partitioned tables (Justin Pryzby)

• Fix ALTER TRIGGER RENAME on partitioned tables to properly rename triggers on all partitions (Arne Roland, Álvaro Herrera)

  Also prohibit cloned triggers from being renamed.

E.3.3.1.2. Indexes

• Allow btree indexes on system and TOAST tables to efficiently store duplicates (Peter Geoghegan)

  Previously de-duplication was disabled for these types of indexes.

• Improve lookup performance of GiST indexes that were built using sorting (Aliaksandr Kalenik, Sergei Shoulbakov, Andrey Borodin)

• Allow unique constraints and indexes to treat NULL values as not distinct (Peter Eisentraut)

  Previously NULL entries were always treated as distinct values, but this can now be changed by creating constraints and indexes using UNIQUE NULLS NOT DISTINCT.

• Allow the ^@ starts-with operator and the starts_with() function to use btree indexes if using the C collation (Tom Lane)

  Previously these could only use SP-GiST indexes.

E.3.3.1.3. Optimizer

• Allow extended statistics to record statistics for a parent with all its children (Tomas Vondra, Justin Pryzby)

  Regular statistics already tracked parent and parent-plus-all-children statistics separately.

• Add server variable recursive_worktable_factor to allow the user to specify the expected size of the working table of a recursive query (Simon Riggs)

E.3.3.1.4. General Performance

• Allow hash lookup for NOT IN clauses with many constants (David Rowley, James Coleman)

  Previously the code always sequentially scanned the list of values.

• Allow SELECT DISTINCT to be parallelized (David Rowley)

• Speed up encoding validation of UTF-8 text by processing 16 bytes at a time (John Naylor, Heikki Linnakangas)

  This will improve text-heavy operations like COPY FROM.

• Improve performance for sorts that exceed work_mem (Heikki Linnakangas)

  When the sort data no longer fits in work_mem, switch to a batch sorting algorithm that uses more output streams than before.

• Improve performance and reduce memory consumption of in-memory sorts (Ronan Dunklau, David Rowley, Thomas Munro, John Naylor)

• Allow WAL full page writes to use LZ4 and Zstandard compression (Andrey Borodin, Justin Pryzby)

  This is controlled by the wal_compression server setting.

• Add support for writing WAL using direct I/O on macOS (Thomas Munro)

  This only works if max_wal_senders = 0 and wal_level = minimal.

• Allow vacuum to be more aggressive in setting the oldest frozen and multi transaction id (Peter Geoghegan)

• Allow a query referencing multiple foreign tables to perform parallel foreign table scans in more cases (Andrey Lepikhov, Etsuro Fujita)

• Improve the performance of window functions that use row_number(), rank(), dense_rank() and count() (David Rowley)

• Improve the performance of spinlocks on high-core-count ARM64 systems (Geoffrey Blake)

E.3.3.1.5. Monitoring

• Enable default logging of checkpoints and slow autovacuum operations (Bharath Rupireddy)

  This changes the default of log_checkpoints to on and that of log_autovacuum_min_duration to 10 minutes. This will cause even an idle server to generate some log output, which might cause problems on resource-constrained servers without log file rotation. These defaults should be changed in such cases.

• Generate progress messages in the server log during slow server starts (Nitin Jadhav, Robert Haas)

  The messages report the cause of the delay. The time interval for notification is controlled by the new server variable log_startup_progress_interval.

• Store cumulative statistics system data in shared memory (Kyotaro Horiguchi, Andres Freund, Melanie Plageman)

  Previously this data was sent to a statistics collector process via UDP packets, and could only be read by sessions after transferring it via the file system. There is no longer a separate statistics collector process.

• Add additional information to VACUUM VERBOSE and autovacuum logging messages (Peter Geoghegan)

• Add EXPLAIN (BUFFERS) output for temporary file block I/O (Masahiko Sawada)

• Allow log output in JSON format (Sehrope Sarkuni, Michael Paquier)

  The new setting is log_destination = jsonlog.

• Allow pg_stat_reset_single_table_counters() to reset the counters of relations shared across all databases (Sadhuprasad Patro)

• Add wait events for local shell commands (Fujii Masao)

  The new wait events are used when calling archive_command, archive_cleanup_command, restore_command and recovery_end_command.

E.3.3.1.6. Privileges

• Allow table accesses done by a view to optionally be controlled by privileges of the view's caller (Christoph Heiss)

  Previously, view accesses were always treated as being done by the view's owner. That's still the default.

• Allow members of the pg_write_server_files predefined role to perform server-side base backups (Dagfinn Ilmari Mannsåker)

  Previously only superusers could perform such backups.

• Allow GRANT to grant permissions to change individual server variables via SET and ALTER SYSTEM (Mark Dilger)

  The new function has_parameter_privilege() reports on this privilege.

• Add predefined role pg_checkpoint that allows members to run CHECKPOINT (Jeff Davis)

  Previously checkpoints could only be run by superusers.

• Allow members of the pg_read_all_stats predefined role to access the views pg_backend_memory_contexts and pg_shmem_allocations (Bharath Rupireddy)

  Previously these views could only be accessed by superusers.

• Allow GRANT to grant permissions on pg_log_backend_memory_contexts() (Jeff Davis)

  Previously this function could only be run by superusers.

E.3.3.1.7. Server Configuration

• Add server variable shared_memory_size to report the size of allocated shared memory (Nathan Bossart)

• Add server variable shared_memory_size_in_huge_pages to report the number of huge memory pages required (Nathan Bossart)

  This is only supported on Linux.

• Honor server variable shared_preload_libraries in single-user mode (Jeff Davis)

  This change supports use of shared_preload_libraries to load custom access methods and WAL resource managers, which would be essential for database access even in single-user mode.

• On Solaris, make the default setting of dynamic_shared_memory_type be sysv (Thomas Munro)

  The previous default choice, posix, can result in spurious failures on this platform.

• Allow postgres -C to properly report runtime-computed values (Nathan Bossart)

  Previously runtime-computed values data_checksums, wal_segment_size, and data_directory_mode would report values that would not be accurate on the running server. However, this does not work on a running server.

E.3.3.2. Streaming Replication And Recovery

• Add support for LZ4 and Zstandard compression of server-side base backups (Jeevan Ladhe, Robert Haas)

• Run the checkpointer and bgwriter processes during crash recovery (Thomas Munro)

  This helps to speed up long crash recoveries.

• Allow WAL processing to pre-fetch needed file contents (Thomas Munro)

  This is controlled by the server variable recovery_prefetch.

• Allow archiving via loadable modules (Nathan Bossart)

  Previously, archiving was only done by calling shell commands. The new server variable archive_library can be set to specify a library to be called for archiving.

• No longer require IDENTIFY_SYSTEM to be run before START_REPLICATION (Jeff Davis)

E.3.3.2.1. Logical Replication

• Allow publication of all tables in a schema (Vignesh C, Hou Zhijie, Amit Kapila)

  For example, this syntax is now supported: CREATE PUBLICATION pub1 FOR TABLES IN SCHEMA s1,s2. ALTER PUBLICATION supports a similar syntax. Tables added later to the listed schemas will also be replicated.

• Allow publication content to be filtered using a WHERE clause (Hou Zhijie, Euler Taveira, Peter Smith, Ajin Cherian, Tomas Vondra, Amit Kapila)

  Rows not satisfying the WHERE clause are not published.

• Allow publication content to be restricted to specific columns (Tomas Vondra, Álvaro Herrera, Rahila Syed)

• Allow skipping of transactions on a subscriber using ALTER SUBSCRIPTION ... SKIP (Masahiko Sawada)

• Add support for prepared (two-phase) transactions to logical replication (Peter Smith, Ajin Cherian, Amit Kapila, Nikhil Sontakke, Stas Kelvich)

  The new CREATE_REPLICATION_SLOT option is called TWO_PHASE. pg_recvlogical now supports a new --two-phase option during slot creation.

• Prevent logical replication of empty transactions (Ajin Cherian, Hou Zhijie, Euler Taveira)

  Previously, publishers would send empty transactions to subscribers if subscribed tables were not modified.

• Add SQL functions to monitor the directory contents of logical replication slots (Bharath Rupireddy)

  The new functions are pg_ls_logicalsnapdir(), pg_ls_logicalmapdir(), and pg_ls_replslotdir(). They can be run by members of the predefined pg_monitor role.

• Allow subscribers to stop the application of logical replication changes on error (Osumi Takamichi, Mark Dilger)

  This is enabled with the subscriber option disable_on_error and avoids possible infinite error loops during stream application.

• Adjust subscriber server variables to match the publisher so datetime and float8 values are interpreted consistently (Japin Li)

  Some publishers might be relying on inconsistent behavior.

• Add system view pg_stat_subscription_stats to report on subscriber activity (Masahiko Sawada)

  The new function pg_stat_reset_subscription_stats() allows resetting these statistics counters.

• Suppress duplicate entries in the pg_publication_tables system view (Hou Zhijie)

  In some cases a partition could appear more than once.

E.3.3.3. Utility Commands

• Add SQL MERGE command to adjust one table to match another (Simon Riggs, Pavan Deolasee, Álvaro Herrera, Amit Langote)

  This is similar to INSERT ... ON CONFLICT but more batch-oriented.

• Add support for HEADER option in COPY text format (Rémi Lapeyre)

  The new option causes the column names to be output, and optionally verified on input.

• Add new WAL-logged method for database creation (Dilip Kumar)

  This is the new default method for copying the template database, as it avoids the need for checkpoints during database creation. However, it might be slow if the template database is large, so the old method is still available.

• Allow CREATE DATABASE to set the database OID (Shruthi Gowda, Antonin Houska)

• Prevent DROP DATABASE, DROP TABLESPACE, and ALTER DATABASE SET TABLESPACE from occasionally failing during concurrent use on Windows (Thomas Munro)

• Allow foreign key ON DELETE SET actions to affect only specified columns (Paul Martinez)

  Previously, all of the columns in the foreign key were always affected.

• Allow ALTER TABLE to modify a table's ACCESS METHOD (Justin Pryzby, Jeff Davis)

• Properly call object access hooks when ALTER TABLE causes table rewrites (Michael Paquier)

• Allow creation of unlogged sequences (Peter Eisentraut)

• Track dependencies on individual columns in the results of functions returning composite types (Tom Lane)

  Previously, if a view or rule contained a reference to a specific column within the result of a composite-returning function, that was not noted as a dependency; the view or rule was only considered to depend on the composite type as a whole. This meant that dropping the individual column would be allowed, causing problems in later use of the view or rule. The column-level dependency is now also noted, so that dropping such a column will be rejected unless the view is changed or dropped.

E.3.3.4. Data Types

• Allow the scale of a numeric value to be negative, or greater than its precision (Dean Rasheed, Tom Lane)

  This allows rounding of values to the left of the decimal point, e.g., '1234'::numeric(4, -2) returns 1200.

• Improve overflow detection when casting values to interval (Joe Koshakow)

• Change the I/O format of type "char" for non-ASCII characters (Tom Lane)

• Update the display width information of modern Unicode characters, like emojis (Jacob Champion)

  Also update from Unicode 5.0 to 14.0.0. There is now an automated way to keep Postgres updated with Unicode releases.

E.3.3.5. Functions

• Add multirange input to range_agg() (Paul Jungwirth)

• Add MIN() and MAX() aggregates for the xid8 data type (Ken Kato)

• Add regular expression functions for compatibility with other relational systems (Gilles Darold, Tom Lane)

  The new functions are regexp_count(), regexp_instr(), regexp_like(), and regexp_substr(). Some new optional arguments were also added to regexp_replace().

• Add the ability to compute the distance between polygons (Tom Lane)

• Add to_char() format codes of, tzh, and tzm (Nitin Jadhav)

  The upper-case equivalents of these were already supported.

• When applying AT TIME ZONE to a time with time zone value, use the transaction start time rather than wall clock time to determine whether DST applies (Aleksander Alekseev, Tom Lane)

  This allows the conversion to be considered stable rather than volatile, and it saves a kernel call per invocation.

• Ignore NULL array elements in ts_delete() and setweight() functions with array arguments (Jean-Christophe Arnu)

  These functions effectively ignore empty-string array elements (since those could never match a valid lexeme). It seems consistent to let them ignore NULL elements too, instead of failing.

• Add support for petabyte units to pg_size_pretty() and pg_size_bytes() (David Christensen)

• Change pg_event_trigger_ddl_commands() to output references to other sessions' temporary schemas using the actual schema name (Tom Lane)

  Previously this function reported all temporary schemas as pg_temp, but it's misleading to use that for any but the current session's temporary schema.

E.3.3.6. PL/PgSQL

• Fix enforcement of PL/pgSQL variable CONSTANT markings (Tom Lane)

  Previously, a variable could be used as a CALL output parameter or refcursor OPEN variable despite being marked CONSTANT.

E.3.3.7. Libpq

• Allow IP address matching against a server certificate's Subject Alternative Name (Jacob Champion)

• Allow PQsslAttribute() to report the SSL library type without requiring a libpq connection (Jacob Champion)

• Change query cancellations sent by the client to use the same TCP settings as normal client connections (Jelte Fennema)

  This allows configured TCP timeouts to apply to query cancel connections.

• Prevent libpq event callback failures from forcing an error result (Tom Lane)

E.3.3.8. Client Applications

• Allow pgbench to retry after serialization and deadlock failures (Yugo Nagata, Marina Polyakova)

E.3.3.8.1. psql

• Improve performance of psql's \copy command, by sending data in larger chunks (Heikki Linnakangas)

• Add \dconfig command to report server variables (Mark Dilger, Tom Lane)

  This is similar to the server-side SHOW command, but it can process patterns to show multiple variables conveniently.

• Add \getenv command to assign the value of an environment variable to a psql variable (Tom Lane)

• Add + option to the \lo_list and \dl commands to show large-object privileges (Pavel Luzanov)

• Add a pager option for the \watch command (Pavel Stehule, Thomas Munro)

  This is only supported on Unix and is controlled by the PSQL_WATCH_PAGER environment variable.

• Make psql include intra-query double-hyphen comments in queries sent to the server (Tom Lane, Greg Nancarrow)

  Previously such comments were removed from the query before being sent. Double-hyphen comments that are before any query text are not sent, and are not recorded as separate psql history entries.

• Adjust psql so that Readline's meta-# command will insert a double-hyphen comment marker (Tom Lane)

  Previously a pound marker was inserted, unless the user had taken the trouble to configure a non-default comment marker.

• Make psql output all results when multiple queries are passed to the server at once (Fabien Coelho)

  Previously, only the last query result was displayed. The old behavior can be restored by setting the SHOW_ALL_RESULTS psql variable to off.

• After an error is detected in --single-transaction mode, change the final COMMIT command to ROLLBACK only if ON_ERROR_STOP is set (Michael Paquier)

  Previously, detection of an error in a -c command or -f script file would lead to issuing ROLLBACK at the end, regardless of the value of ON_ERROR_STOP.

• Improve psql's tab completion (Shinya Kato, Dagfinn Ilmari Mannsåker, Peter Smith, Koyu Tanigawa, Ken Kato, David Fetter, Haiying Tang, Peter Eisentraut, Álvaro Herrera, Tom Lane, Masahiko Sawada)

• Limit support of psql's backslash commands to servers running PostgreSQL 9.2 or later (Tom Lane)

  Remove code that was only used when running with an older server. Commands that do not require any version-specific adjustments compared to 9.2 will still work.

E.3.3.8.2. pg_dump

• Make pg_dump dump public schema ownership changes and security labels (Noah Misch)

• Improve performance of dumping databases with many objects (Tom Lane)

  This will also improve the performance of pg_upgrade.

• Improve parallel pg_dump's performance for tables with large TOAST tables (Tom Lane)

• Add dump/restore option --no-table-access-method to force restore to only use the default table access method (Justin Pryzby)

• Limit support of pg_dump and pg_dumpall to servers running PostgreSQL 9.2 or later (Tom Lane)

E.3.3.9. Server Applications

• Add new pg_basebackup option --target to control the base backup location (Robert Haas)

  The new options are server to write the backup locally and blackhole to discard the backup (for testing).

• Allow pg_basebackup to do server-side gzip, LZ4, and Zstandard compression and client-side LZ4 and Zstandard compression of base backup files (Dipesh Pandit, Jeevan Ladhe)

  Client-side gzip compression was already supported.

• Allow pg_basebackup to compress on the server side and decompress on the client side before storage (Dipesh Pandit)

  This is accomplished by specifying compression on the server side and plain output format.

• Allow pg_basebackup's --compress option to control the compression location (server or client), compression method, and compression options (Michael Paquier, Robert Haas)

• Add the LZ4 compression method to pg_receivewal (Georgios Kokolatos)

  This is enabled via --compress=lz4 and requires binaries to be built using --with-lz4.

• Add additional capabilities to pg_receivewal's --compress option (Georgios Kokolatos)

• Improve pg_receivewal's ability to restart at the proper WAL location (Ronan Dunklau)

  Previously, pg_receivewal would start based on the WAL file stored in the local archive directory, or at the sending server's current WAL flush location. With this change, if the sending server is running Postgres 15 or later, the local archive directory is empty, and a replication slot is specified, the replication slot's restart point will be used.

• Add pg_rewind option --config-file to simplify use when server configuration files are stored outside the data directory (Gunnar Bluth)

E.3.3.9.1. pg_upgrade

• Store pg_upgrade's log and temporary files in a subdirectory of the new cluster called pg_upgrade_output.d (Justin Pryzby)

  Previously such files were left in the current directory, requiring manual cleanup. Now they are automatically removed on successful completion of pg_upgrade.

• Disable default status reporting during pg_upgrade operation if the output is not a terminal (Andres Freund)

  The status reporting output can be enabled for non-tty usage by using --verbose.

• Make pg_upgrade report all databases with invalid connection settings (Jeevan Ladhe)

  Previously only the first database with an invalid connection setting was reported.

• Make pg_upgrade preserve tablespace and database OIDs, as well as relation relfilenode numbers (Shruthi Gowda, Antonin Houska)

• Add a --no-sync option to pg_upgrade (Michael Paquier)

  This is recommended only for testing.

• Limit support of pg_upgrade to old servers running PostgreSQL 9.2 or later (Tom Lane)

E.3.3.9.2. pg_waldump

• Allow pg_waldump output to be filtered by relation file node, block number, fork number, and full page images (David Christensen, Thomas Munro)

• Make pg_waldump report statistics before an interrupted exit (Bharath Rupireddy)

  For example, issuing a control-C in a terminal running pg_waldump --stats --follow will report the current statistics before exiting. This does not work on Windows.

• Improve descriptions of some transaction WAL records reported by pg_waldump (Masahiko Sawada, Michael Paquier)

• Allow pg_waldump to dump information about multiple resource managers (Heikki Linnakangas)

  This is enabled by specifying the --rmgr option multiple times.

E.3.3.10. Documentation

• Add documentation for pg_encoding_to_char() and pg_char_to_encoding() (Ian Lawrence Barwick)

• Document the ^@ starts-with operator (Tom Lane)

E.3.3.11. Source Code

• Add support for continuous integration testing using cirrus-ci (Andres Freund, Thomas Munro, Melanie Plageman)

• Add configure option --with-zstd to enable Zstandard builds (Jeevan Ladhe, Robert Haas, Michael Paquier)

• Add an ABI identifier field to the magic block in loadable libraries, allowing non-community PostgreSQL distributions to identify libraries that are not compatible with other builds (Peter Eisentraut)

  An ABI field mismatch will generate an error at load time.

• Create a new pg_type.typcategory value for "char" (Tom Lane)

  Some other internal-use-only types have also been assigned to this category.

• Add new protocol message TARGET to specify a new COPY method to be used for base backups (Robert Haas)

  pg_basebackup now uses this method.

• Add new protocol message COMPRESSION and COMPRESSION_DETAIL to specify the compression method and options (Robert Haas)

• Remove server support for old BASE_BACKUP command syntax and base backup protocol (Robert Haas)

• Add support for extensions to set custom backup targets (Robert Haas)

• Allow extensions to define custom WAL resource managers (Jeff Davis)

• Add function pg_settings_get_flags() to get the flags of server variables (Justin Pryzby)

• On Windows, export all the server's global variables using PGDLLIMPORT markers (Robert Haas)

  Previously, only specific variables were accessible to extensions on Windows.

• Require GNU make version 3.81 or later to build PostgreSQL (Tom Lane)

• Require OpenSSL to build the pgcrypto extension (Peter Eisentraut)

• Require Perl version 5.8.3 or later (Dagfinn Ilmari Mannsåker)

• Require Python version 3.2 or later (Andres Freund)

E.3.3.12. Additional Modules

• Allow amcheck to check sequences (Mark Dilger)

• Improve amcheck sanity checks for TOAST tables (Mark Dilger)

• Add new module basebackup_to_shell as an example of a custom backup target (Robert Haas)

• Add new module basic_archive as an example of performing archiving via a library (Nathan Bossart)

• Allow btree_gist indexes on boolean columns (Emre Hasegeli)

  These can be used for exclusion constraints.

• Fix pageinspect's page_header() to handle 32-kilobyte page sizes (Quan Zongliang)

  Previously, improper negative values could be returned in certain cases.

• Add counters for temporary file block I/O to pg_stat_statements (Masahiko Sawada)

• Add JIT counters to pg_stat_statements (Magnus Hagander)

• Add new module pg_walinspect (Bharath Rupireddy)

  This gives SQL-level output similar to pg_waldump.

• Indicate the permissive/enforcing state in sepgsql log messages (Dave Page)

E.3.3.12.1. postgres_fdw

• Allow postgres_fdw to push down CASE expressions (Alexander Pyhalov)

• Add server variable postgres_fdw.application_name to control the application name of postgres_fdw connections (Hayato Kuroda)

  Previously the remote session's application_name could only be set on the remote server or via a postgres_fdw connection specification. postgres_fdw.application_name supports some escape sequences for customization, making it easier to tell such connections apart on the remote server.

• Allow parallel commit on postgres_fdw servers (Etsuro Fujita)

  This is enabled with the CREATE SERVER option parallel_commit.

E.3.4. Acknowledgments

The following individuals (in alphabetical order) have contributed to this release as patch authors, committers, reviewers, testers, or reporters of issues.