+ Previously this combination caused a parse error.
- rather than using a binary encoding.
- connection name.
+ directly, rather than using an encoded form.
- The function is
- linkend="libpq-pqresultmemorysize">PQresultMemorySize() .
+ This allows statements to be associated with named connections,
+ so future operations like cursors don't need to re-reference the
+ connection name.
- Remove the no-display/debug flag from the libpq
- options parameter (Peter Eisentraut)
-
-
- This allows the option to be used by
+ Add PREPARE AS support to
+
+ Allow vacuumdb to disable waiting for locks or skipping all-visible
+ pages (Nathan Bossart)
+
+
+ The options are --skip-locked and
+ --disable-page-skipping .
+
+
+
+
+
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"
+ PG_COLORS="error=01;31:warning=01;35:locus=01" .
-->
- Allow values produced by queries to be assigned to pgbench
- variables (Fabien Coelho, Álvaro Herrera)
+ Allow values produced by queries to be assigned
+ to
pgbench variables (Fabien Coelho,
+ Álvaro Herrera)
- The commands is \gset .
+ The command for thi s is \gset .
2018-10-15 [5b75a4f82] pgbench: Report errors during run better
-->
- Improve pgbench error reporting with clearer messages and return
+ Improve pgbench's error reporting with clearer messages and return
codes (Peter Eisentraut)
-
- Allow vacuumdb to disable waiting for locks or skipping all-visible
- pages (Nathan Bossart)
-
-
- The options are --skip-locked and
- --disable-page-skipping .
-
-
-
-
-
-->
- Allow to use the file system cloning
- feature (Peter Eisentraut)
+ Allow to use the file system's cloning
+ feature, if there is one (Peter Eisentraut)
-->
- Allow specification of the
pg_upgrade
- socket directory (Daniel Gustafsson)
+ Allow specification of the socket directory to use
+
in pg_upgrade (Daniel Gustafsson)
- This is controlled by --socketdir ; the default
+ This is controlled by --socketdir ; the default
is the current directory.
+
+
+
+ Fix to report accurate
+ open_datasync durations on
+
+
+
-->
- Allow control over the number of rows each
- statement uses (Surafel Temesgen, David Rowley)
+ 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 is --rows-per-insert .
-
-
-
-
-
-
- Add --exclude-database option to
-
pg_dumpall (Andrew Dunstan)
+ The option controlling this is --rows-per-insert .
-->
- Allow pg_dump to emit INSERT ... ON CONFLICT DO
- NOTHING (Surafel Temesgen)
+ Allow
pg_dump to emit INSERT
+ ... ON CONFLICT DO NOTHING (Surafel Temesgen)
This avoids conflict failures during restore.
- --on-conflict-do-nothing .
+ The option is --on-conflict-do-nothing .
-->
- Decouple the order of parallel
pg_dump
- from the order used by
pg_restore
- (Tom Lane)
+ 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
- efficient parallel restores.
+ 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 number of float digits to be specified
+ Allow the setting to be
+
specified for
pg_dump and
pg_dumpall (Andrew Dunstan)
- This allows the float digit output to match previous dumps.
+ 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.
-
+
- Fix to report accurate
- open_datasync durations on
-
-
+ Add --exclude-database option to
+
pg_dumpall (Andrew Dunstan)
+
+
- Add support function capability to improve optimizer estimates,
+ Add planner support
+ function interfaces to improve optimizer estimates,
inlining, and indexing for functions (Tom Lane)
- Reserve a range of OIDs (9000-9999) to be used for external
- extensions (Andres Freund)
+ 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
+ linkend="system-catalog-oid-assignment">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.
- A strong random source is now required.
+ A strong random-number source is now required.
- Properly report Winsock errors on
+ 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-
supported compiler, and
MSVC
+ Require a C99-
compliant compiler, and
MSVC
2013 or later on
Windows (Andres Freund)
-
-
-
-
-
-
Documentation
-
-
-
- Add images to the
PostgreSQL
- documentation (Jürgen Purtz)
+ not
lynx , for generating plain-text
+ documentation output files (Peter Eisentraut)
-
-
-
-
- More clearly document the problems of server failure during
- linkend="backup-lowlevel-base-backup-exclusive">exclusive base
- backups (David Steele, Robert Haas)
-
-
-
-
-
-
- Document that the B /bytes units can be specified
- for server variables
- (Greg Stark)
-
-
-
-
-
-
- Add documentation
- for aclitem functions and operators (Fabien Coelho,
- John Naylor)
+ 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.
- Update documentation on the use of
- linkend="creating-cluster-nfs">
NFS
- (Peter Eisentraut)
+ Support use of images in the
PostgreSQL
+ documentation (Jürgen Purtz)
-->
- Allow more ORDER BY sorts and
- LIMIT clauses to be pushed to
-
postgres_fdw foreign tables (Etsuro
- Fujita)
+ Allow ORDER BY sorts
+ and LIMIT clauses to be pushed
+ to foreign servers in more
+ cases (Etsuro Fujita)
-->
- Improve optimizer cost accounting for pushdown of aggregates to
- tables (Etsuro Fujita)
-
-
- This release also improves costing of
-
postgres_fdw target list generation.
+ Improve optimizer cost accounting for
+
postgres_fdw queries (Etsuro Fujita)
-->
- Update <application>unaccent> rules with new
+ Update <xref linkend="unaccent"/ > rules with new
punctuation and symbols (Hugh Ranalli, Michaël Paquier)
-->
- Allow <xref linkend="unaccent"/> to handle some accents encoded
- as combining characters (Hugh Ranalli)
+ Allow <application>unaccent to handle some accents
+ encoded as combining characters (Hugh Ranalli)
-
- Add 64-bit hash function to (Amul Sul)
-
-
- The function citext_hash_extended() also
- requires a seed value. NO DOCS?
-
-
-
-
-
-
- Add 64-bit hash function to (Amul Sul)
-
-
- The function hstore_hash_extended() also
- requires a seed value. NO DOCS?
-
-
-
-
-
- Add a parameter to a function to check
- each index tuple from the root of the tree.
+ Add a parameter to
+ 's bt_index_parent_check()
+ function to check each index tuple from the root of the tree
+ (Peter Geoghegan)