-Previously, multiple different recovery_target* variables could be specified, and the last one specified was honored. Now, only one can be specified, though the same one can
-be specified multiple times and the last specification is honored.
-
+
+ Previously, multiple different recovery_target*
+ variables could be specified, and the last one specified was
+ honored. Now, only one can be specified, though the same one can
+ be specified multiple times and the last specification is honored.
2019-04-05 [478cacb50] Ensure consistent name matching behavior in processSQLNa
-->
-
-Allow data type name to use non-C collations (Tom Lane, Daniel Vérité)
-
+
+ Allow data type
+ linkend="datatype-character-special-table">name to use
+ non-C collations (Tom Lane, Daniel Vérité)
+
-
-It still uses the "C" collation by default, rather than defaulting to the database collation. Regular expression operations on data type name columns will now use the
-"C" collation; you will need to override the collation if you want to use locale-specific regular expression patterns, e.g., \w.
-
+
+ It still uses the "C" collation by default, rather than defaulting
+ to the database collation. Regular expression operations on
+ data type name columns will now use the "C" collation; you will
+ need to override the collation if you want to use locale-specific
2019-03-21 [bfb456c1b] Improve error reporting for DROP FUNCTION/PROCEDURE/AGGR
-->
-
-Cause DROP IF EXISTS FUNCTION/PROCEDURE/AGGREGATE/ROUTINE to generate an error if no arguments are supplied and there are multiple matching objects (David Rowley)
-
+
+ Cause DROP IF EXISTS
+ FUNCTION/PROCEDURE/AGGREGATE/ROUTINE
+ to generate an error if no arguments are supplied and there are
2019-04-09 [947613127] Prevent inlining of multiply-referenced CTEs with outer
-->
-
-Allow common table expressions (CTE) to be inlined in later parts of the query (Andreas Karlsson, Andrew Gierth, David Fetter, Tom Lane)
-
+
+ Allow common table expressions
+ (CTE) to be inlined in later parts of the query
+ (Andreas Karlsson, Andrew Gierth, David Fetter, Tom Lane)
+
-
-Specifically, CTEs are inlined if they are not recursive and are referenced only once later in the query. Inlining can be prevented by specifying MATERIALIZED, and
-forced by specifying NOT MATERIALIZED. Previously, CTEs were never inlined and were always evaluated before the rest of the query.
-
+
+ Specifically, CTEs are inlined
+ if they are not recursive and are referenced only
+ once later in the query. Inlining can be prevented by
2018-12-14 [5e0928005] Make pg_statistic and related code account more honestly
-->
-
-Store statistics using the collation defined for each column (Tom Lane)
-
+
+ Store statistics using the collation defined for each column
+ (Tom Lane)
+
-
-Previously, the default collation was used for all statistics storage. This potentially gives better optimizer behavior for columns with non-default collations.
-
+
+ Previously, the default collation was used for all statistics
+ storage. This potentially gives better optimizer behavior for
2018-12-18 [6b0faf723] Make collation-aware system catalog columns use "C" coll
-->
-
-Use "C" collation for information_schema and the system tables (Tom Lane)
-
+
+ Use "C" collation for information_schema
+ and the system tables (Tom Lane)
+
-
-This will produce more consistent behavior in databases with different collations, but will also cause these tables to produce results in "C" collation ordering, rather
-than the default collation for the database.
-
+
+ This will produce more consistent behavior in databases with
+ different collations, but will also cause these tables to produce
+ results in "C" collation ordering, rather than the default
2018-10-09 [212fab992] Relax transactional restrictions on ALTER TYPE ... ADD V
-->
-
-Allow enumerated values to be added in more transaction types (Andrew Dunstan, Tom Lane, Thomas Munro)
-
+
+ Allow enumerated values to be added in more transaction types
+ (Andrew Dunstan, Tom Lane, Thomas Munro)
+
-
-Previously, ALTER TYPE ... ADD VALUE could only be called in a transaction that created the enumerated type. Now, the only restriction is that the new enumerated value
-cannot be referenced until the transaction commits.
-
+
+ Previously, ALTER
+ TYPE ... ADD VALUE could only be called in
+ a transaction that created the enumerated type. Now, the only
+ restriction is that the new enumerated value cannot be referenced
2018-09-21 [121213d9d] Improve tab completion for ANALYZE, EXPLAIN, and VACUUM.
-->
-
-Improve tab completion of CREATE TABLE, CREATE TRIGGER, CREATE EVENT TRIGGER, ANALYZE, EXPLAIN, VACUUM, ALTER TABLE, ALTER INDEX, ALTER DATABASE, ALTER INDEX ALTER COLUMN (Dagfinn Ilmari Mannsåker, Tatsuro Yamada, Michaël Paquier, Tom Lane, Justin Pryzby)
-
+
+ Improve tab completion of CREATE TABLE, CREATE TRIGGER,
+ CREATE EVENT TRIGGER, ANALYZE, EXPLAIN, VACUUM, ALTER TABLE,
+ ALTER INDEX, ALTER DATABASE, ALTER INDEX ALTER COLUMN
+ (Dagfinn Ilmari Mannsåker, Tatsuro Yamada, Michaël Paquier,
2018-07-08 [a45adc747] Fix WITH CHECK OPTION on views referencing postgres_fdw
-->
-
-Properly honor WITH CHECK OPTION on views that reference postgres_fdw tables (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 release enforces CHECK
-OPTIONs on them. Previously, only INSERTs and UPDATEs with RETURNING clauses that returned CHECK OPTION values were validated.
-
+
+ While CHECK OPTIONs on
+ postgres_fdw tables are ignored (because
+ the reference is foreign), views on such tables are considered
projects / postgresql.git / commitdiff