+
+
Release 9.2.23
+
+
+
Release date:
+
+
+ This release contains a small number of fixes from 9.2.22.
+ For information about new features in the 9.2 major release, see
+ .
+
+
+ The
PostgreSQL community will stop releasing updates+ for the 9.2.X release series in September 2017.
+ Users are encouraged to update to a newer release branch soon.
+
+
+
+
Migration to Version 9.2.23
+
+ A dump/restore is not required for those running 9.2.X.
+
+
+ However, if you are upgrading from a version earlier than 9.2.22,
+ see .
+
+
+
+
+
+
Changes
+
+
+
+
+ Show foreign tables
+ in information_schema.table_privileges
+ view (Peter Eisentraut)
+
+
+ All other relevant information_schema views include
+ foreign tables, but this one ignored them.
+
+
+ Since this view definition is installed by
initdb,+ merely upgrading will not fix the problem. If you need to fix this
+ in an existing installation, you can, as a superuser, do this
+BEGIN;
+DROP SCHEMA information_schema CASCADE;
+\i SHAREDIR/information_schema.sql
+COMMIT;
+
+ (Run pg_config --sharedir if you're uncertain
+ where SHAREDIR is.) This must be repeated in each
+ database to be fixed.
+
+
+
+
+ Clean up handling of a fatal exit (e.g., due to receipt
+ of SIGTERM) that occurs while trying to execute
+ a ROLLBACK of a failed transaction (Tom Lane)
+
+
+ This situation could result in an assertion failure. In production
+ builds, the exit would still occur, but it would log an unexpected
+ message about cannot drop active portal.
+
+
+
+
+ Remove assertion that could trigger during a fatal exit (Tom Lane)
+
+
+
+
+ Correctly identify columns that are of a range type or domain type over
+ a composite type or domain type being searched for (Tom Lane)
+
+
+ Certain ALTER commands that change the definition of a
+ composite type or domain type are supposed to fail if there are any
+ stored values of that type in the database, because they lack the
+ infrastructure needed to update or check such values. Previously,
+ these checks could miss relevant values that are wrapped inside range
+ types or sub-domains, possibly allowing the database to become
+ inconsistent.
+
+
+
+
+ Change
ecpg's parser to allow RETURNING+ clauses without attached C variables (Michael Meskes)
+
+
+ This allows
ecpg programs to contain SQL constructs+ that use RETURNING internally (for example, inside a CTE)
+ rather than using it to define values to be returned to the client.
+
+
+
+
+ Improve selection of compiler flags for PL/Perl on Windows (Tom Lane)
+
+
+ This fix avoids possible crashes of PL/Perl due to inconsistent
+ assumptions about the width of time_t values.
+ A side-effect that may be visible to extension developers is
+ that _USE_32BIT_TIME_T is no longer defined globally
+ in
PostgreSQL Windows builds. This is not expected+ to cause problems, because type time_t is not used
+ in any
PostgreSQL API definitions.+
+
+
+
+
+
+
+
Release 9.2.22
+
+
Release 9.3.19
+
+
+
Release date:
+
+
+ This release contains a small number of fixes from 9.3.18.
+ For information about new features in the 9.3 major release, see
+ .
+
+
+
+
Migration to Version 9.3.19
+
+ A dump/restore is not required for those running 9.3.X.
+
+
+ However, if you are upgrading from a version earlier than 9.3.18,
+ see .
+
+
+
+
+
+
Changes
+
+
+
+
+ Show foreign tables
+ in information_schema.table_privileges
+ view (Peter Eisentraut)
+
+
+ All other relevant information_schema views include
+ foreign tables, but this one ignored them.
+
+
+ Since this view definition is installed by
initdb,+ merely upgrading will not fix the problem. If you need to fix this
+ in an existing installation, you can, as a superuser, do this
+BEGIN;
+DROP SCHEMA information_schema CASCADE;
+\i SHAREDIR/information_schema.sql
+COMMIT;
+
+ (Run pg_config --sharedir if you're uncertain
+ where SHAREDIR is.) This must be repeated in each
+ database to be fixed.
+
+
+
+
+ Clean up handling of a fatal exit (e.g., due to receipt
+ of SIGTERM) that occurs while trying to execute
+ a ROLLBACK of a failed transaction (Tom Lane)
+
+
+ This situation could result in an assertion failure. In production
+ builds, the exit would still occur, but it would log an unexpected
+ message about cannot drop active portal.
+
+
+
+
+ Remove assertion that could trigger during a fatal exit (Tom Lane)
+
+
+
+
+ Correctly identify columns that are of a range type or domain type over
+ a composite type or domain type being searched for (Tom Lane)
+
+
+ Certain ALTER commands that change the definition of a
+ composite type or domain type are supposed to fail if there are any
+ stored values of that type in the database, because they lack the
+ infrastructure needed to update or check such values. Previously,
+ these checks could miss relevant values that are wrapped inside range
+ types or sub-domains, possibly allowing the database to become
+ inconsistent.
+
+
+
+
+ Fix crash in
pg_restore when using parallel mode and+ using a list file to select a subset of items to restore (Tom Lane)
+
+
+
+
+ Change
ecpg's parser to allow RETURNING+ clauses without attached C variables (Michael Meskes)
+
+
+ This allows
ecpg programs to contain SQL constructs+ that use RETURNING internally (for example, inside a CTE)
+ rather than using it to define values to be returned to the client.
+
+
+
+
+ Improve selection of compiler flags for PL/Perl on Windows (Tom Lane)
+
+
+ This fix avoids possible crashes of PL/Perl due to inconsistent
+ assumptions about the width of time_t values.
+ A side-effect that may be visible to extension developers is
+ that _USE_32BIT_TIME_T is no longer defined globally
+ in
PostgreSQL Windows builds. This is not expected+ to cause problems, because type time_t is not used
+ in any
PostgreSQL API definitions.+
+
+
+
+
+
+
+
Release 9.3.18
projects / postgresql.git / commitdiff