The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 12.1, 11.6, 10.11, 9.6.16, 9.5.20, and 9.4.25. This release fixes over 60 bugs reported over the last three months.
PostgreSQL 9.4 will stop receiving fixes on February 13, 2020, which is the next planned cumulative update release. Please see our versioning policy for more information.
This update also fixes over 50 bugs that were reported in the last several months. Some of these issues affect only version 12, but may also affect all supported versions.
Some of these fixes include:
ALTER TABLEadds a column without a default value along with other changes that require a table rewrite
VACUUMthat would cause it to fail under a specific case involving a still-running transaction.
VACUUMruns on a GiST index.
CLUSTERon an expression index.
SET CONSTRAINTS ... DEFERREDon partitioned tables.
bitshiftright()where it failed to zero out padding space in the last byte if the bit string length is not a multiple of 8. For how to correct your data, please see the "Updating" section.
position()functions returns 1, as per the SQL standard.
recovery_min_apply_delaysettings during crash recovery.
pg_dumpnow outputs similarly named triggers and RLS policies in order based on table name, instead of OID.
pg_rewindto not update the contents of
pg_controlwhen using the
This update also contains tzdata release 2019c for DST law changes in Fiji and Norfolk Island. Historical corrections for Alberta, Austria, Belgium, British Columbia, Cambodia, Hong Kong, Indiana (Perry County), Kaliningrad, Kentucky, Michigan, Norfolk Island, South Korea, and Turkey.
For the full list of changes available, please review the release notes.
All PostgreSQL update releases are cumulative. As with other minor releases,
users are not required to dump and reload their database or use
order to apply this update release; you may simply shutdown PostgreSQL and
update its binaries.
Users who have skipped one or more update releases may need to run additional, post-update steps; please see the release notes for earlier versions for details.
If you have inconsistent data as a result of saving the output of
bitshiftright() in a table, it's possible to fix it with a query similar to:
UPDATE mytab SET bitcol = ~(~bitcol) WHERE bitcol != ~(~bitcol);
NOTE: PostgreSQL 9.4 will stop receiving fixes on February 13, 2020. Please see our versioning policy for more information.