Upgrading from 11.8 to 12.3 gives you 242 fixes

List of changes:

• ⇑ Upgrade to 12 released on 2019-10-03 - docs

  • Remove the special behavior of oid columns (Andres Freund, John Naylor)

    Previously, a normally-invisible oid column could be specified during table creation using WITH OIDS; that ability has been removed. Columns can still be explicitly declared as type oid. Operations on tables that have columns created using WITH OIDS will need adjustment.

    The system catalogs that previously had hidden oid columns now have ordinary oid columns. Hence, SELECT * will now output those columns, whereas previously they would be displayed only if selected explicitly.

  • Remove data types abstime, reltime, and tinterval (Andres Freund)

    These are obsoleted by SQL-standard types such as timestamp.

  • Remove the timetravel extension (Andres Freund)

  • Move recovery.conf settings into postgresql.conf (Masao Fujii, Simon Riggs, Abhijit Menon-Sen, Sergei Kornilov)

    recovery.conf is no longer used, and the server will not start if that file exists. recovery.signal and standby.signal files are now used to switch into non-primary mode. The trigger_file setting has been renamed to promote_trigger_file. The standby_mode setting has been removed.

  • Do not allow multiple conflicting recovery_target* specifications (Peter Eisentraut)

    Specifically, only allow one of recovery_target, recovery_target_lsn, recovery_target_name, recovery_target_time, and recovery_target_xid. Previously, multiple different instances of these parameters could be specified, and the last one was honored. Now, only one can be specified, though the same one can be specified multiple times and the last specification is honored.

  • Cause recovery to advance to the latest timeline by default (Peter Eisentraut)

    Specifically, recovery_target_timeline now defaults to latest. Previously, it defaulted to current.

  • Refactor code for geometric functions and operators (Emre Hasegeli)

    This could lead to more accurate, but slightly different, results compared to previous releases. Notably, cases involving NaN, underflow, overflow, and division by zero are handled more consistently than before.

  • Improve performance by using a new algorithm for output of real and double precision values (Andrew Gierth)

    Previously, displayed floating-point values were rounded to 6 (for real) or 15 (for double precision) digits by default, adjusted by the value of extra_float_digits. Now, whenever extra_float_digits is more than zero (as it now is by default), only the minimum number of digits required to preserve the exact binary value are output. The behavior is the same as before when extra_float_digits is set to zero or less.

    Also, formatting of floating-point exponents is now uniform across platforms: two digits are used unless three are necessary. In previous releases, Windows builds always printed three digits.

  • random() and setseed() now behave uniformly across platforms (Tom Lane)

    The sequence of random() values generated following a setseed() call with a particular seed value is likely to be different now than before. However, it will also be repeatable, which was not previously guaranteed because of interference from other uses of random numbers inside the server. The SQL random() function now has its own private per-session state to forestall that.

  • Change SQL-style substring() to have standard-compliant greediness behavior (Tom Lane)

    In cases where the pattern can be matched in more than one way, the initial sub-pattern is now treated as matching the least possible amount of text rather than the greatest; for example, a pattern such as %#"aa*#"% now selects the first group of a's from the input, not the last group.

  • Do not pretty-print the result of xpath() or the XMLTABLE construct (Tom Lane)

    In some cases, these functions would insert extra whitespace (newlines and/or spaces) in nodeset values. This is undesirable since depending on usage, the whitespace might be considered semantically significant.

  • Rename command-line tool pg_verify_checksums to pg_checksums (Michaël Paquier)

  • In pg_restore, require specification of -f - to send the dump contents to standard output (Euler Taveira)

    Previously, this happened by default if no destination was specified, but that was deemed to be unfriendly.

  • Disallow non-unique abbreviations in psql's \pset format command (Daniel Vérité)

    Previously, for example, \pset format a chose aligned; it will now fail since that could equally well mean asciidoc.

  • In new btree indexes, the maximum index entry length is reduced by eight bytes, to improve handling of duplicate entries (Peter Geoghegan)

    This means that a REINDEX operation on an index pg_upgrade'd from a previous release could potentially fail.

  • Cause DROP IF EXISTS FUNCTION/PROCEDURE/AGGREGATE/ROUTINE to generate an error if no argument list is supplied and there are multiple matching objects (David Rowley)

    Also improve the error message in such cases.

  • Split the pg_statistic_ext catalog into two catalogs, and add the pg_stats_ext view of it (Dean Rasheed, Tomas Vondra)

    This change supports hiding potentially-sensitive statistics data from unprivileged users.

  • Remove obsolete pg_constraint.consrc column (Peter Eisentraut)

  • Remove obsolete pg_attrdef.adsrc column (Peter Eisentraut)

  • Mark table columns of type name as having “C” collation by default (Tom Lane, Daniel Vérité)

    The comparison operators for data type name can now use any collation, rather than always using “C” collation. To preserve the previous semantics of queries, columns of type name are now explicitly marked as having “C” collation. A side effect of this is that regular-expression operators on name columns will now use the “C” collation by default, not the database collation, to determine the behavior of locale-dependent regular expression patterns (such as \w). If you want non-C behavior for a regular expression on a name column, attach an explicit COLLATE clause. (For user-defined name columns, another possibility is to specify a different collation at table creation time; but that just moves the non-backwards-compatibility to the comparison operators.)

  • Treat object-name columns in the information_schema views as being of type name, not varchar (Tom Lane)

    Per the SQL standard, object-name columns in the information_schema views are declared as being of domain type sql_identifier. In PostgreSQL, the underlying catalog columns are really of type name. This change makes sql_identifier be a domain over name, rather than varchar as before. This eliminates a semantic mismatch in comparison and sorting behavior, which can greatly improve the performance of queries on information_schema views that restrict an object-name column. Note however that inequality restrictions, for example

    SELECT ... FROM information_schema.tables WHERE table_name < 'foo';
    

    will now use “C”-locale comparison semantics by default, rather than the database's default collation as before. Sorting on these columns will also follow “C” ordering rules. The previous behavior (and inefficiency) can be enforced by adding a COLLATE "default" clause.

  • Remove the ability to disable dynamic shared memory (Kyotaro Horiguchi)

    Specifically, dynamic_shared_memory_type can no longer be set to none.

  • Parse libpq integer connection parameters more strictly (Fabien Coelho)

    In previous releases, using an incorrect integer value for connection parameters connect_timeout, keepalives, keepalives_count, keepalives_idle, keepalives_interval and port resulted in libpq either ignoring those values or failing with incorrect error messages.

  • Improve performance of many operations on partitioned tables (Amit Langote, David Rowley, Tom Lane, Álvaro Herrera)

    Allow tables with thousands of child partitions to be processed efficiently by operations that only affect a small number of partitions.

  • Allow foreign keys to reference partitioned tables (Álvaro Herrera)

  • Improve speed of COPY into partitioned tables (David Rowley)

  • Allow partition bounds to be any expression (Kyotaro Horiguchi, Tom Lane, Amit Langote)

    Such expressions are evaluated at partitioned-table creation time. Previously, only simple constants were allowed as partition bounds.

  • Allow CREATE TABLE's tablespace specification for a partitioned table to affect the tablespace of its children (David Rowley, Álvaro Herrera)

  • Avoid sorting when partitions are already being scanned in the necessary order (David Rowley)

  • ALTER TABLE ATTACH PARTITION is now performed with reduced locking requirements (Robert Haas)

  • Add partition introspection functions (Michaël Paquier, Álvaro Herrera, Amit Langote)

    The new function pg_partition_root() returns the top-most parent of a partition tree, pg_partition_ancestors() reports all ancestors of a partition, and pg_partition_tree() displays information about partitions.

  • Include partitioned indexes in the system view pg_indexes (Suraj Kharage)

  • Add psql command \dP to list partitioned tables and indexes (Pavel Stehule)

  • Improve psql \d and \z display of partitioned tables (Pavel Stehule, Michaël Paquier, Álvaro Herrera)

  • Fix bugs that could cause ALTER TABLE DETACH PARTITION to leave behind incorrect dependency state, allowing subsequent operations to misbehave, for example by not dropping a former partition child index when its table is dropped (Tom Lane)

  • Improve performance and space utilization of btree indexes with many duplicates (Peter Geoghegan, Heikki Linnakangas)

    Previously, duplicate index entries were stored unordered within their duplicate groups. This caused overhead during index inserts, wasted space due to excessive page splits, and it reduced VACUUM's ability to recycle entire pages. Duplicate index entries are now sorted in heap-storage order.

    Indexes pg_upgrade'd from previous releases will not have these benefits.

  • Allow multi-column btree indexes to be smaller (Peter Geoghegan, Heikki Linnakangas)

    Internal pages and min/max leaf page indicators now only store index keys until the change key, rather than all indexed keys. This also improves the locality of index access.

    Indexes pg_upgrade'd from previous releases will not have these benefits.

  • Improve speed of btree index insertions by reducing locking overhead (Alexander Korotkov)

  • Support INCLUDE columns in GiST indexes (Andrey Borodin)

  • Add support for nearest-neighbor (KNN) searches of SP-GiST indexes (Nikita Glukhov, Alexander Korotkov, Vlad Sterzhanov)

  • Reduce the WAL write overhead of GiST, GIN, and SP-GiST index creation (Anastasia Lubennikova, Andrey V. Lepikhov)

  • Allow index-only scans to be more efficient on indexes with many columns (Konstantin Knizhnik)

  • Improve the performance of vacuum scans of GiST indexes (Andrey Borodin, Konstantin Kuznetsov, Heikki Linnakangas)

  • Delete empty leaf pages during GiST VACUUM (Andrey Borodin)

  • Reduce locking requirements for index renaming (Peter Eisentraut)

  • Allow CREATE STATISTICS to create most-common-value statistics for multiple columns (Tomas Vondra)

    This improves optimization for queries that test several columns, requiring an estimate of the combined effect of several WHERE clauses. If the columns are correlated and have non-uniform distributions then multi-column statistics will allow much better estimates.

  • Allow common table expressions (CTEs) to be inlined into the outer query (Andreas Karlsson, Andrew Gierth, David Fetter, Tom Lane)

    Specifically, CTEs are automatically inlined if they have no side-effects, are not recursive, and are referenced only once in the query. Inlining can be prevented by specifying MATERIALIZED, or forced for multiply-referenced CTEs by specifying NOT MATERIALIZED. Previously, CTEs were never inlined and were always evaluated before the rest of the query.

  • Allow control over when generic plans are used for prepared statements (Pavel Stehule)

    This is controlled by the plan_cache_mode server parameter.

  • Improve optimization of partition and UNION ALL queries that have only a single child (David Rowley)

  • Improve processing of domains that have no check constraints (Tom Lane)

    Domains that are being used purely as type aliases no longer cause optimization difficulties.

  • Pre-evaluate calls of LEAST and GREATEST when their arguments are constants (Vik Fearing)

  • Improve optimizer's ability to verify that partial indexes with IS NOT NULL conditions are usable in queries (Tom Lane, James Coleman)

    Usability can now be recognized in more cases where the calling query involves casts or large x IN (array) clauses.

  • Compute ANALYZE statistics using the collation defined for each column (Tom Lane)

    Previously, the database's default collation was used for all statistics. This potentially gives better optimizer behavior for columns with non-default collations.

  • Improve selectivity estimates for inequality comparisons on ctid columns (Edmund Horner)

  • Improve optimization of joins on columns of type tid (Tom Lane)

    These changes primarily improve the efficiency of self-joins on ctid columns.

  • Fix the leakproofness designations of some btree comparison operators and support functions (Tom Lane)

    This allows some optimizations that previously would not have been applied in the presence of security barrier views or row-level security.

  • Enable Just-in-Time (JIT) compilation by default, if the server has been built with support for it (Andres Freund)

    Note that this support is not built by default, but has to be selected explicitly while configuring the build.

  • Speed up keyword lookup (John Naylor, Joerg Sonnenberger, Tom Lane)

  • Improve search performance for multi-byte characters in position() and related functions (Heikki Linnakangas)

  • Allow toasted values to be minimally decompressed (Paul Ramsey)

    This is useful for routines that only need to examine the initial portion of a toasted field.

  • Allow ALTER TABLE ... SET NOT NULL to avoid unnecessary table scans (Sergei Kornilov)

    This can be optimized when the table's column constraints can be recognized as disallowing nulls.

  • Allow ALTER TABLE ... SET DATA TYPE changing between timestamp and timestamptz to avoid a table rewrite when the session time zone is UTC (Noah Misch)

    In the UTC time zone, these two data types are binary compatible.

  • Improve speed in converting strings to int2 or int4 integers (Andres Freund)

  • Allow parallelized queries when in SERIALIZABLE isolation mode (Thomas Munro)

    Previously, parallelism was disabled when in this mode.

  • Use pread() and pwrite() for random I/O (Oskari Saarenmaa, Thomas Munro)

    This reduces the number of system calls required for I/O.

  • Improve the speed of setting the process title on FreeBSD (Thomas Munro)

  • Allow logging of statements from only a percentage of transactions (Adrien Nayrat)

    The parameter log_transaction_sample_rate controls this.

  • Add progress reporting to CREATE INDEX and REINDEX operations (Álvaro Herrera, Peter Eisentraut)

    Progress is reported in the pg_stat_progress_create_index system view.

  • Add progress reporting to CLUSTER and VACUUM FULL (Tatsuro Yamada)

    Progress is reported in the pg_stat_progress_cluster system view.

  • Add progress reporting to pg_checksums (Michael Banck, Bernd Helmle)

    This is enabled with the option --progress.

  • Add counter of checksum failures to pg_stat_database (Magnus Hagander)

  • Add tracking of global objects in system view pg_stat_database (Julien Rouhaud)

    Global objects are shown with a pg_stat_database.datid value of zero.

  • Add the ability to list the contents of the archive directory (Christoph Moench-Tegeder)

    The function is pg_ls_archive_statusdir().

  • Add the ability to list the contents of temporary directories (Nathan Bossart)

    The function, pg_ls_tmpdir(), optionally allows specification of a tablespace.

  • Add information about the client certificate to the system view pg_stat_ssl (Peter Eisentraut)

    The new columns are client_serial and issuer_dn. Column clientdn has been renamed to client_dn for clarity.

  • Restrict visibility of rows in pg_stat_ssl for unprivileged users (Peter Eisentraut)

  • At server start, emit a log message including the server version number (Christoph Berg)

  • Prevent logging “incomplete startup packet” if a new connection is immediately closed (Tom Lane)

    This avoids log spam from certain forms of monitoring.

  • Include the application_name, if set, in log_connections log messages (Don Seiler)

  • Make the walreceiver set its application name to the cluster name, if set (Peter Eisentraut)

  • Add the timestamp of the last received standby message to pg_stat_replication (Lim Myungkyu)

  • Add a wait event for fsync of WAL segments (Konstantin Knizhnik)

  • Add GSSAPI encryption support (Robbie Harwood, Stephen Frost)

    This feature allows TCP/IP connections to be encrypted when using GSSAPI authentication, without having to set up a separate encryption facility such as SSL. In support of this, add hostgssenc and hostnogssenc record types in pg_hba.conf for selecting connections that do or do not use GSSAPI encryption, corresponding to the existing hostssl and hostnossl record types. There is also a new gssencmode libpq option, and a pg_stat_gssapi system view.

  • Allow the clientcert pg_hba.conf option to check that the database user name matches the client certificate's common name (Julian Markwort, Marius Timmer)

    This new check is enabled with clientcert=verify-full.

  • Allow discovery of an LDAP server using DNS SRV records (Thomas Munro)

    This avoids the requirement of specifying ldapserver. It is only supported if PostgreSQL is compiled with OpenLDAP.

  • Add ability to enable/disable cluster checksums using pg_checksums (Michael Banck, Michaël Paquier)

    The cluster must be shut down for these operations.

  • Reduce the default value of autovacuum_vacuum_cost_delay to 2ms (Tom Lane)

    This allows autovacuum operations to proceed faster by default.

  • Allow vacuum_cost_delay to specify sub-millisecond delays, by accepting fractional values (Tom Lane)

  • Allow time-based server parameters to use units of microseconds (us) (Tom Lane)

  • Allow fractional input for integer server parameters (Tom Lane)

    For example, SET work_mem = '30.1GB' is now allowed, even though work_mem is an integer parameter. The value will be rounded to an integer after any required units conversion.

  • Allow units to be defined for floating-point server parameters (Tom Lane)

  • Add wal_recycle and wal_init_zero server parameters to control WAL file recycling (Jerry Jelinek)

    Avoiding file recycling can be beneficial on copy-on-write file systems like ZFS.

  • Add server parameter tcp_user_timeout to control the server's TCP timeout (Ryohei Nagaura)

  • Allow control of the minimum and maximum SSL protocol versions (Peter Eisentraut)

    The server parameters are ssl_min_protocol_version and ssl_max_protocol_version.

  • Add server parameter ssl_library to report the SSL library version used by the server (Peter Eisentraut)

  • Add server parameter shared_memory_type to control the type of shared memory to use (Andres Freund)

    This allows selection of System V shared memory, if desired.

  • Allow some recovery parameters to be changed with reload (Peter Eisentraut)

    These parameters are archive_cleanup_command, promote_trigger_file, recovery_end_command, and recovery_min_apply_delay.

  • Allow the streaming replication timeout (wal_sender_timeout) to be set per connection (Takayuki Tsunakawa)

    Previously, this could only be set cluster-wide.

  • Add function pg_promote() to promote standbys to primaries (Laurenz Albe, Michaël Paquier)

    Previously, this operation was only possible by using pg_ctl or creating a trigger file.

  • Allow replication slots to be copied (Masahiko Sawada)

    The functions for this are pg_copy_physical_replication_slot() and pg_copy_logical_replication_slot().

  • Make max_wal_senders not count as part of max_connections (Alexander Kukushkin)

  • Add an explicit value of current for recovery_target_timeline (Peter Eisentraut)

  • Make recovery fail if a two-phase transaction status file is corrupt (Michaël Paquier)

    Previously, a warning was logged and recovery continued, allowing the transaction to be lost.

  • Add REINDEX CONCURRENTLY option to allow reindexing without locking out writes (Michaël Paquier, Andreas Karlsson, Peter Eisentraut)

    This is also controlled by the reindexdb application's --concurrently option.

  • Add support for generated columns (Peter Eisentraut)

    The content of generated columns are computed from expressions (including references to other columns in the same table) rather than being specified by INSERT or UPDATE commands.

  • Add a WHERE clause to COPY FROM to control which rows are accepted (Surafel Temesgen)

    This provides a simple way to filter incoming data.

  • Allow enumerated values to be added more flexibly (Andrew Dunstan, Tom Lane, Thomas Munro)

    Previously, ALTER TYPE ... ADD VALUE could not be called in a transaction block, unless it was part of the same transaction that created the enumerated type. Now it can be called in a later transaction, so long as the new enumerated value is not referenced until after it is committed.

  • Add commands to end a transaction and start a new one (Peter Eisentraut)

    The commands are COMMIT AND CHAIN and ROLLBACK AND CHAIN.

  • Add VACUUM and CREATE TABLE options to prevent VACUUM from truncating trailing empty pages (Takayuki Tsunakawa)

    These options are vacuum_truncate and toast.vacuum_truncate. Use of these options reduces VACUUM's locking requirements, but prevents returning disk space to the operating system.

  • Allow VACUUM to skip index cleanup (Masahiko Sawada)

    This change adds a VACUUM command option INDEX_CLEANUP as well as a table storage option vacuum_index_cleanup. Use of this option reduces the ability to reclaim space and can lead to index bloat, but it is helpful when the main goal is to freeze old tuples.

  • Add the ability to skip VACUUM and ANALYZE operations on tables that cannot be locked immediately (Nathan Bossart)

    This option is called SKIP_LOCKED.

  • Allow VACUUM and ANALYZE to take optional Boolean argument specifications (Masahiko Sawada)

  • Prevent TRUNCATE, VACUUM and ANALYZE from requesting a lock on tables for which the user lacks permission (Michaël Paquier)

    This prevents unauthorized locking, which could interfere with user queries.

  • Add EXPLAIN option SETTINGS to output non-default optimizer settings (Tomas Vondra)

    This output can also be obtained when using auto_explain by setting auto_explain.log_settings.

  • Add OR REPLACE option to CREATE AGGREGATE (Andrew Gierth)

  • Allow modifications of system catalogs' options using ALTER TABLE (Peter Eisentraut)

    Modifications of catalogs' reloptions and autovacuum settings are now supported. (Setting allow_system_table_mods is still required.)

  • Use all key columns' names when selecting default constraint names for foreign keys (Peter Eisentraut)

    Previously, only the first column name was included in the constraint name, resulting in ambiguity for multi-column foreign keys.

  • Update assorted knowledge about Unicode to match Unicode 12.1.0 (Peter Eisentraut)

    This fixes, for example, cases where psql would misformat output involving combining characters.

  • Update Snowball stemmer dictionaries with support for new languages (Arthur Zakirov)

    This adds word stemming support for Arabic, Indonesian, Irish, Lithuanian, Nepali, and Tamil to full text search.

  • Allow creation of collations that report string equality for strings that are not bit-wise equal (Peter Eisentraut)

    This feature supports “nondeterministic” collations that can define case- and accent-agnostic equality comparisons. Thus, for example, a case-insensitive uniqueness constraint on a text column can be made more easily than before. This is only supported for ICU collations.

  • Add support for ICU collation attributes on older ICU versions (Peter Eisentraut)

    This allows customization of the collation rules in a consistent way across all ICU versions.

  • Allow data type name to more seamlessly be compared to other text types (Tom Lane)

    Type name now behaves much like a domain over type text that has default collation “C”. This allows cross-type comparisons to be processed more efficiently.

  • Add support for the SQL/JSON path language (Nikita Glukhov, Teodor Sigaev, Alexander Korotkov, Oleg Bartunov, Liudmila Mantrova)

    This allows execution of complex queries on JSON values using an SQL-standard language.

  • Add support for hyperbolic functions (Lætitia Avrot)

    Also add log10() as an alias for log(), for standards compliance.

  • Improve the accuracy of statistical aggregates like variance() by using more precise algorithms (Dean Rasheed)

  • Allow date_trunc() to have an additional argument to control the time zone (Vik Fearing, Tom Lane)

    This is faster and simpler than using the AT TIME ZONE clause.

  • Adjust to_timestamp()/to_date() functions to be more forgiving of template mismatches (Artur Zakirov, Alexander Korotkov, Liudmila Mantrova)

    This new behavior more closely matches the Oracle functions of the same name.

  • Fix assorted bugs in XML functions (Pavel Stehule, Markus Winand, Chapman Flack)

    Specifically, in XMLTABLE, xpath(), and xmlexists(), fix some cases where nothing was output for a node, or an unexpected error was thrown, or necessary escaping of XML special characters was omitted.

  • Allow the BY VALUE clause in XMLEXISTS and XMLTABLE (Chapman Flack)

    This SQL-standard clause has no effect in PostgreSQL's implementation, but it was unnecessarily being rejected.

  • Prevent current_schema() and current_schemas() from being run by parallel workers, as they are not parallel-safe (Michaël Paquier)

  • Allow RECORD and RECORD[] to be used as column types in a query's column definition list for a table function that is declared to return RECORD (Elvis Pranskevichus)

  • Allow SQL commands and variables with the same names as those commands to be used in the same PL/pgSQL function (Tom Lane)

    For example, allow a variable called comment to exist in a function that calls the COMMENT SQL command. Previously this combination caused a parse error.

  • Add new optional warning and error checks to PL/pgSQL (Pavel Stehule)

    The new checks allow for run-time validation of INTO column counts and single-row results.

  • Add connection parameter tcp_user_timeout to control libpq's TCP timeout (Ryohei Nagaura)

  • Allow libpq (and thus psql) to report only the SQLSTATE value in error messages (Didier Gautheron)

  • Add libpq function PQresultMemorySize() to report the memory used by a query result (Lars Kanis, Tom Lane)

  • Remove the no-display/debug flag from libpq's options connection parameter (Peter Eisentraut)

    This allows this parameter to be set by postgres_fdw.

  • Allow ecpg to create variables of data type bytea (Ryo Matsumura)

    This allows ECPG clients to interact with bytea data directly, rather than using an encoded form.

  • Add PREPARE AS support to ECPG (Ryo Matsumura)

  • Allow vacuumdb to select tables for vacuum based on their wraparound horizon (Nathan Bossart)

    The options are --min-xid-age and --min-mxid-age.

  • Allow vacuumdb to disable waiting for locks or skipping all-visible pages (Nathan Bossart)

    The options are --skip-locked and --disable-page-skipping.

  • Add colorization to the output of command-line utilities (Peter Eisentraut)

    This is enabled by setting the environment variable PG_COLOR to always or auto. The specific colors used can be adjusted by setting the environment variable PG_COLORS, using ANSI escape codes for colors. For example, the default behavior is equivalent to PG_COLORS="error=01;31:warning=01;35:locus=01".

  • Add CSV table output mode in psql (Daniel Vérité)

    This is controlled by \pset format csv or the command-line --csv option.

  • Show the manual page URL in psql's \help output for a SQL command (Peter Eisentraut)

  • Display the IP address in psql's \conninfo (Fabien Coelho)

  • Improve tab completion of CREATE TABLE, CREATE TRIGGER, CREATE EVENT TRIGGER, ANALYZE, EXPLAIN, VACUUM, ALTER TABLE, ALTER INDEX, ALTER DATABASE, and ALTER INDEX ALTER COLUMN (Dagfinn Ilmari Mannsåker, Tatsuro Yamada, Michaël Paquier, Tom Lane, Justin Pryzby)

  • Allow values produced by queries to be assigned to pgbench variables (Fabien Coelho, Álvaro Herrera)

    The command for this is \gset.

  • Improve precision of pgbench's --rate option (Tom Lane)

  • Improve pgbench's error reporting with clearer messages and return codes (Peter Eisentraut)

  • Allow control of log file rotation via pg_ctl (Kyotaro Horiguchi, Alexander Kuzmenkov, Alexander Korotkov)

    Previously, this was only possible via an SQL function or a process signal.

  • Properly detach the new server process during pg_ctl start (Paul Guo)

    This prevents the server from being shut down if the shell script that invoked pg_ctl is interrupted later.

  • Allow pg_upgrade to use the file system's cloning feature, if there is one (Peter Eisentraut)

    The --clone option has the advantages of --link, while preventing the old cluster from being changed after the new cluster has started.

  • Allow specification of the socket directory to use in pg_upgrade (Daniel Gustafsson)

    This is controlled by --socketdir; the default is the current directory.

  • Allow pg_checksums to disable fsync operations (Michaël Paquier)

    This is controlled by the --no-sync option.

  • Allow pg_rewind to disable fsync operations (Michaël Paquier)

  • Fix pg_test_fsync to report accurate open_datasync durations on Windows (Laurenz Albe)

  • When pg_dump emits data with INSERT commands rather than COPY, allow more than one data row to be included in each INSERT (Surafel Temesgen, David Rowley)

    The option controlling this is --rows-per-insert.

  • Allow pg_dump to emit INSERT ... ON CONFLICT DO NOTHING (Surafel Temesgen)

    This avoids conflict failures during restore. The option is --on-conflict-do-nothing.

  • Decouple the order of operations in a parallel pg_dump from the order used by a subsequent parallel pg_restore (Tom Lane)

    This allows pg_restore to perform more-fully-parallelized parallel restores, especially in cases where the original dump was not done in parallel. Scheduling of a parallel pg_dump is also somewhat improved.

  • Allow the extra_float_digits setting to be specified for pg_dump and pg_dumpall (Andrew Dunstan)

    This is primarily useful for making dumps that are exactly comparable across different source server versions. It is not recommended for normal use, as it may result in loss of precision when the dump is restored.

  • Add --exclude-database option to pg_dumpall (Andrew Dunstan)

  • Add CREATE ACCESS METHOD command to create new table types (Andres Freund, Haribabu Kommi, Álvaro Herrera, Alexander Korotkov, Dmitry Dolgov)

    This enables the development of new table access methods, which can optimize storage for different use cases. The existing heap access method remains the default.

  • Add planner support function interfaces to improve optimizer estimates, inlining, and indexing for functions (Tom Lane)

    This allows extensions to create planner support functions that can provide function-specific selectivity, cost, and row-count estimates that can depend on the function's arguments. Support functions can also supply simplified representations and index conditions, greatly expanding optimization possibilities.

  • Simplify renumbering manually-assigned OIDs, and establish a new project policy for management of such OIDs (John Naylor, Tom Lane)

    Patches that manually assign OIDs for new built-in objects (such as new functions) should now randomly choose OIDs in the range 8000—9999. At the end of a development cycle, the OIDs used by committed patches will be renumbered down to lower numbers, currently somewhere in the 4xxx range, using the new renumber_oids.pl script. This approach should greatly reduce the odds of OID collisions between different in-process patches.

    While there is no specific policy reserving any OIDs for external use, it is recommended that forks and other projects needing private manually-assigned OIDs use numbers in the high 7xxx range. This will avoid conflicts with recently-merged patches, and it should be a long time before the core project reaches that range.

  • Build Cygwin binaries using dynamic instead of static libraries (Marco Atzeri)

  • Remove configure switch --disable-strong-random (Michaël Paquier)

    A strong random-number source is now required.

  • printf-family functions, as well as strerror and strerror_r, now behave uniformly across platforms within Postgres code (Tom Lane)

    Notably, printf understands %m everywhere; on Windows, strerror copes with Winsock error codes (it used to do so in backend but not frontend code); and strerror_r always follows the GNU return convention.

  • Require a C99-compliant compiler, and MSVC 2013 or later on Windows (Andres Freund)

  • Use pandoc, not lynx, for generating plain-text documentation output files (Peter Eisentraut)

    This affects only the INSTALL file generated during make dist and the seldom-used plain-text postgres.txt output file. Pandoc produces better output than lynx and avoids some locale/encoding issues. Pandoc version 1.13 or later is required.

  • Support use of images in the PostgreSQL documentation (Jürgen Purtz)

  • Allow ORDER BY sorts and LIMIT clauses to be pushed to postgres_fdw foreign servers in more cases (Etsuro Fujita)

  • Improve optimizer cost accounting for postgres_fdw queries (Etsuro Fujita)

  • Properly honor WITH CHECK OPTION on views that reference postgres_fdw tables (Etsuro Fujita)

    While CHECK OPTIONs on postgres_fdw tables are ignored (because the reference is foreign), views on such tables are considered local, so this change enforces CHECK OPTIONs on them. Previously, only INSERTs and UPDATEs with RETURNING clauses that returned CHECK OPTION values were validated.

  • Allow pg_stat_statements_reset() to be more granular (Haribabu Kommi, Amit Kapila)

    The function now allows reset of statistics for specific databases, users, and queries.

  • Allow control of the auto_explain log level (Tom Dunstan, Andrew Dunstan)

    The default is LOG.

  • Update unaccent rules with new punctuation and symbols (Hugh Ranalli, Michaël Paquier)

  • Allow unaccent to handle some accents encoded as combining characters (Hugh Ranalli)

  • Allow unaccent to remove accents from Greek characters (Tasos Maschalidis)

  • Add a parameter to amcheck's bt_index_parent_check() function to check each index tuple from the root of the tree (Peter Geoghegan)

  • Improve oid2name and vacuumlo option handling to match other commands (Tatsuro Yamada)

• ⇑ Upgrade to 12.1 released on 2019-11-14 - docs

  • Fix crash when ALTER TABLE adds a column without a default value along with making other changes that require a table rewrite (Andres Freund)

  • Fix lock handling in REINDEX CONCURRENTLY (Michael Paquier)

    REINDEX CONCURRENTLY neglected to take a session-level lock on the new index version, potentially allowing other sessions to manipulate it too soon. Also, a query-cancel or session-termination interrupt arriving at the wrong time could result in failure to release the session-level locks that REINDEX CONCURRENTLY does hold.

  • Avoid crash due to race condition when reporting the progress of a CREATE INDEX CONCURRENTLY or REINDEX CONCURRENTLY command (Álvaro Herrera)

  • Avoid creating duplicate dependency entries during REINDEX CONCURRENTLY (Michael Paquier)

    This bug resulted in bloat in pg_depend, but no worse consequences than that.

  • Fix “wrong type of slot” error when trying to CLUSTER on an expression index (Andres Freund)

  • Fix dropping of indexed columns in partitioned tables (Amit Langote, Michael Paquier)

    Previously this might fail with an error message complaining about the dependencies of the indexes. It should automatically drop the indexes, instead.

  • Ensure that a partition index can be dropped after a failure to reindex it concurrently (Michael Paquier)

    The index's pg_class.relispartition flag was left in the wrong state in such a case, causing DROP INDEX to fail.

  • Fix handling of equivalence class members for partition-wise joins (Amit Langote)

    This oversight could lead either to failure to use a feasible partition-wise join plan, or to a “could not find pathkey item to sort” planner failure.

  • Fix crash triggered by an EvalPlanQual recheck on a table with a BEFORE UPDATE trigger (Andres Freund)

  • Ignore restore_command, recovery_end_command, and recovery_min_apply_delay settings during crash recovery (Fujii Masao)

    Now that these settings can be specified in postgresql.conf, they could be turned on during crash recovery, but honoring them then is undesirable. Ignore these settings until crash recovery is complete.

  • Fix result of text position() function (also known as strpos()) for an empty search string (Tom Lane)

    Historically, and per the SQL standard, the result should be one in such cases, but 12.0 returned zero.

  • Avoid memory leak while vacuuming a GiST index (Dilip Kumar)

  • Fix libpq to allow trailing whitespace in the string values of integer parameters (Michael Paquier)

    Version 12 tightened libpq's validation of integer parameters, but disallowing trailing whitespace seems undesirable.

  • In libpq, correctly report CONNECTION_BAD connection status after a failure caused by a syntactically invalid connect_timeout parameter value (Lars Kanis)

  • Fix scheduling of parallel restore of a foreign key constraint on a partitioned table (Álvaro Herrera)

    pg_dump failed to emit full dependency information for partitioned tables' foreign keys. This could allow parallel pg_restore to try to recreate a foreign key constraint too soon.

  • In pg_upgrade, reject tables with columns of type sql_identifier, as that has changed representation in version 12 (Tomas Vondra)

  • In pg_rewind with the --dry-run option, avoid updating pg_control (Alexey Kondratov)

    This could lead to failures in subsequent pg_rewind attempts.

  • Put back pqsignal() as an exported libpq symbol (Tom Lane)

    This function was removed on the grounds that no clients should be using it, but that turns out to break usage of current libpq with very old versions of psql, and perhaps other applications.

• ⇑ Upgrade to 12.2 released on 2020-02-13 - docs

  • Fix TRUNCATE ... CASCADE to ensure all relevant partitions are truncated (Jehan-Guillaume de Rorthais)

    If a partition of a partitioned table is truncated with the CASCADE option, and the partitioned table has a foreign-key reference from another table, that table must also be truncated. The need to check this was missed if the referencing table was itself partitioned, possibly allowing rows to survive that violate the foreign-key constraint.

    Hence, if you have foreign key constraints between partitioned tables, and you have done any partition-level TRUNCATE on the referenced table, you should check to see if any foreign key violations exist. The simplest way is to add a new instance of the foreign key constraint (and, once that succeeds, drop it or the original constraint). That may be prohibitive from a locking standpoint, however, in which case you might prefer to manually query for unmatched rows.

  • Fix failure to attach foreign key constraints to sub-partitions (Jehan-Guillaume de Rorthais)

    When adding a partition to a level below the first level of a multi-level partitioned table, foreign key constraints referencing the top partitioned table were not cloned to the new partition, leading to possible constraint violations later. Detaching and re-attaching the new partition is the cheapest way to fix this. However, if there are many partitions to be fixed, adding a new instance of the foreign key constraint might be preferable.

  • Fix possible crash during concurrent update on a partitioned table or inheritance tree (Tom Lane)

  • Fix base backup to handle database OIDs larger than INT32_MAX (Peter Eisentraut)

  • Fix crash during recursive page split in GiST index build (Heikki Linnakangas)

  • Fix failure in ALTER TABLE when a column referenced in a GENERATED expression has been added or changed in type earlier in the same ALTER command (Tom Lane)

  • Fix unlikely panic in the checkpointer process, caused by opening relation segments that might already have been removed (Thomas Munro)

  • Fix handling of multiple AFTER ROW triggers on a foreign table (Etsuro Fujita)

  • Ensure that the <> operator for type char reports indeterminate-collation errors as such, rather than as “cache lookup failed for collation 0” (Tom Lane)

  • Avoid treating TID scans as sequential scans (Tatsuhito Kasahara)

    A refactoring oversight caused TID scans (selection by CTID) to be counted as sequential scans in the statistics views, and to take whole-table predicate locks as sequential scans do. The latter behavior could cause unnecessary serialization errors in serializable transaction mode.

  • Reduce spinlock contention when there are many active walsender processes (Pierre Ducroquet)

  • Fix EXPLAIN's SETTINGS option to print as empty in non-text output formats (Tom Lane)

    In the non-text output formats, fields are supposed to appear when requested, even if they have empty or zero values.

  • Fix planner errors induced by overly-aggressive collapsing of joins to single-row subqueries (Tom Lane)

    This mistake led to errors such as “failed to construct the join relation”.

  • Fix “no = operator for opfamily NNNN” planner error when trying to match a LIKE or regex pattern-match operator to a binary-compatible index opclass (Tom Lane)

  • Fix incorrect estimation for OR clauses when using most-common-value extended statistics (Tomas Vondra)

  • Fix bugs in handling of non-blocking I/O when using GSSAPI encryption (Tom Lane)

    These errors could result in dropping data (usually leading to subsequent wire-protocol-violation errors) or in a “livelock” situation where a sending process goes to sleep although not all its data has been sent. Moreover, libpq failed to keep separate encryption state for each connection, creating the possibility for failures in applications using multiple encrypted database connections.

  • Avoid crash after an out-of-memory failure in ecpglib (Tom Lane)

  • Fix handling of a corner-case error result from Windows' ReadFile() function (Thomas Munro, Juan José Santamaría Flecha)

    So far as is known, this oversight just resulted in noisy log messages, not any actual query misbehavior.

  • On Windows, work around sharing violations for the postmaster's log file when pg_ctl is used to start the postmaster very shortly after it's been stopped, for example by pg_ctl restart (Alexander Lakhin)

• ⇑ Upgrade to 12.3 released on 2020-05-14 - docs

  • Fix possible failure with GENERATED columns (David Rowley)

    If a GENERATED column's value is an exact copy of another column of the table (and it is a pass-by-reference data type), it was possible to crash or insert corrupted data into the table. While it would be rather pointless for a GENERATED expression to just duplicate another column, an expression using a function that sometimes returns its input unchanged could create the situation.

  • Handle inheritance of generated columns better (Peter Eisentraut)

    When a table column is inherited during CREATE TABLE ... INHERITS, disallow changing any generation properties when the parent column is already marked GENERATED; but allow a child column to be marked GENERATED when its parent is not.

  • Fix cross-column references in CREATE TABLE LIKE INCLUDING GENERATED (Peter Eisentraut)

    CREATE TABLE ... LIKE failed when trying to copy a GENERATED expression that references a physically-later column.

  • Preserve the indisclustered setting of indexes rebuilt by REINDEX CONCURRENTLY (Justin Pryzby)

  • Fix crash when COLLATE is applied to a non-collatable type in a partition bound expression (Dmitry Dolgov)

  • Repair performance regression in floating point overflow/underflow detection (Emre Hasegeli)

    Previous refactoring had resulted in isinf() being called extra times in some hot code paths.

  • Fix server's connection-startup logic for case where a GSSAPI connection is rejected because support is not compiled in, and the client then tries SSL instead (Andrew Gierth)

    This led to a bogus “unsupported frontend protocol” failure.

  • Fix memory leakage during GSSAPI encryption (Tom Lane)

    Both the backend and libpq would leak memory equivalent to the total amount of data sent during the session, if GSSAPI encryption is in use.

  • Fix query-lifespan memory leak for a set-returning function used in a query's FROM clause (Andres Freund)

  • Improve planner's handling of no-op domain coercions (Tom Lane)

    Fix some cases where a domain coercion that does nothing was not completely removed from expressions.

  • Avoid race condition when ANALYZE replaces the catalog tuple for extended statistics data (Dean Rasheed)

  • Remove ill-considered skip of “redundant” anti-wraparound vacuums (Michael Paquier)

    This avoids a corner case where autovacuum could get into a loop of repeatedly trying and then skipping the same vacuum job.

  • Ensure INCLUDE'd columns are always removed from B-tree pivot tuples (Peter Geoghegan)

    This mistake wasted space in some rare cases, but was otherwise harmless.

  • Cope with invalid TOAST indexes that could be left over after a failed REINDEX CONCURRENTLY (Julien Rouhaud)

  • Ensure that valid index dependencies are left behind after a failed REINDEX CONCURRENTLY (Michael Paquier)

    Previously the old index could be left with no pg_depend links at all, so that for example it would not get dropped if the parent table is dropped.

  • Avoid possible failure after a replication slot copy, due to premature removal of WAL data (Masahiko Sawada, Arseny Sher)

  • Ensure that generated columns are correctly handled during updates issued by logical replication (Peter Eisentraut)

  • Fix crash in psql when attempting to re-establish a failed connection (Michael Paquier)

  • Ensure that pg_basebackup generates valid tar files (Robert Haas)

    In some cases a partial block of zeroes would be added to the end of the file. While this seems to be harmless with common versions of tar, it's not OK per the POSIX file format spec.

  • Make pg_checksums skip tablespace subdirectories that belong to a different PostgreSQL major version (Michael Banck, Bernd Helmle)

    Such subdirectories don't really belong to our database cluster, and so must not be processed.

  • Ignore temporary copies of pg_internal.init in pg_checksums and related programs (Michael Paquier)

  • On Windows, avoid premature creation of postmaster's log file during pg_ctl start (Alexander Lakhin)

    The previous coding could allow the file to be created with permissions that wouldn't allow the postmaster to write on it.

  • On Windows, set console VT100 compatibility mode in programs that support PG_COLOR colorization (Juan José Santamaría Flecha)

    Without this, the colorization option doesn't actually work.

  • Stop requiring extra parentheses in ereport() calls (Andres Freund, Tom Lane)

  • Fix Makefile dependencies for libpq and ecpg (Dagfinn Ilmari Mannsåker)

• source repo
• author info
• meta-info