%c>) in
+ linkend="guc-log-line-prefix">log_line_prefix>
+ always output four hex digits after the period (Bruce Momjian)
+
+
+
+
+
+
+
+
+
Other
+
+
+
+
+ Throw an error if expiring tuple is again updated or deleted (Kevin Grittner)
+ DETAILS?
+
+
+
+
+ Change ON UPDATE
+ SET NULL/SET DEFAULT> foreign key actions to affect
+ all referenced columns, not just those referenced in the
+ UPDATE> (Tom Lane)
+
+
+ Previously only columns referenced in the UPDATE> were
+ set to null or DEFAULT>.
+
+
+
+
+ Internally store default foreign key matches (non-FULL>,
+ non-PARTIAL>) as simple> (Tom Lane)
+
+
+ These were previously stored as "<unspecified>".
+ This changes the value stored in system column
+ linkend="catalog-pg-constraint">pg_constraint.confmatchtype>.
+
+
+
+
+ Store
WAL> in a continuous
+ stream, rather than skipping the last 16MB segment every 4GB
+ (Heikki Linnakangas)
+
+
+ Previously,
WAL> files ending in FF> were
+ not used. If you have
WAL> backup or restore scripts
+ that took that skipping into account, they need to be adjusted.
+
+
+
+
+
-
- Improve grouping of sessions waiting for
- linkend="guc-commit-delay">commit_delay>
- (Peter Geoghegan)
-
-
- This improves the usefulness and behavior of
- commit_delay>. BACKWARD COMPATIBILITY
-
-
-
Allow in-memory sorts to use their full memory allocation (Jeff Janes)
-
- Require superuser privileges to set
- linkend="guc-commit-delay">commit_delay>
- because it can now potentially delay other sessions (Simon Riggs)
- BACKWARD COMPATIBILITY
-
-
-
-
Remove the external
-
- Have
session id> (%c>) in
- linkend="guc-log-line-prefix">log_line_prefix>
- always output four hex digits after the period (Bruce Momjian)
- COMPATIBILITY
-
-
-
-
- Rename
replication_timeout> to
- linkend="guc-wal-sender-timeout">wal_sender_timeout>
- (Amit Kapila)
-
-
- BACKWARD COMPATIBILITY
- This setting controls the
WAL> sender timeout.
-
-
-
-
- Store
WAL> in a continuous stream, rather than skipping
- the last 16MB segment every 4GB (Heikki Linnakangas) BACKWARD
- COMPATIBLE BREAK
-
-
- Previously,
WAL> files ending in FF> were
- not used. If you have
WAL> backup or restore scripts
- that took that skipping into account, they need to be adjusted.
-
-
-
Change the
WAL> record format to allow splitting the record header
-
- Throw an error if expiring tuple is again updated or deleted (Kevin Grittner)
- DETAILS? BACKWARD INCOMPATIBILITY
-
-
-
Have REASSIGN
-
- Change ON UPDATE
- SET NULL/SET DEFAULT> foreign key actions to affect
- all referenced columns, not just those referenced in the
- UPDATE> (Tom Lane)
-
-
- Previously only columns referenced in the UPDATE> were
- set to null or DEFAULT>. BACKWARD COMPATIBILITY CHANGE
-
-
-
Provide clients with
-
- Internally store default foreign key matches (non-FULL>,
- non-PARTIAL>) as simple> (Tom Lane)
-
-
- These were previously stored as "<unspecified>".
- This changes the value stored in system column
- linkend="catalog-pg-constraint">pg_constraint.confmatchtype>.
- BACKWARD COMPATIBILITY CHANGE
-
-
-