diff --git a/doc/src/sgml/release-9.3.sgml b/doc/src/sgml/release-9.3.sgml index 9cb916282f75ccab9d024098465bbd450b8fb342..f15f5ec17f7c4a03025ed2e1240e5975fd2b35ed 100644 --- a/doc/src/sgml/release-9.3.sgml +++ b/doc/src/sgml/release-9.3.sgml @@ -41,8 +41,111 @@ - ADD HERE - here + Server Settings + + + + + + Rename replication_timeout to wal_sender_timeout + (Amit Kapila) + + + + This setting controls the WAL sender timeout. + + + + + + Improve grouping of sessions waiting for commit_delay + (Peter Geoghegan) + + + + This improves the usefulness and behavior of + commit_delay. + + + + + + Require superuser privileges to set commit_delay + because it can now potentially delay other sessions (Simon Riggs) + + + + + + Have session id (%c) in 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 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. + + + + + @@ -182,19 +285,6 @@ - - - Improve grouping of sessions waiting for 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) @@ -408,16 +498,6 @@ - - - Require superuser privileges to set commit_delay - because it can now potentially delay other sessions (Simon Riggs) - BACKWARD COMPATIBILITY - - - - Remove the external @@ -425,15 +505,6 @@ - - - Have session id (%c) in log_line_prefix - always output four hex digits after the period (Bruce Momjian) - COMPATIBILITY - - - @@ -550,19 +621,6 @@ - - - Rename replication_timeout to wal_sender_timeout - (Amit Kapila) - - - - BACKWARD COMPATIBILITY - This setting controls the WAL sender timeout. - - - @@ -571,20 +629,6 @@ - - - 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 @@ -675,13 +719,6 @@ - - - Throw an error if expiring tuple is again updated or deleted (Kevin Grittner) - DETAILS? BACKWARD INCOMPATIBILITY - - - Have REASSIGN @@ -727,20 +764,6 @@ - - - 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 pg_constraint.confmatchtype. - BACKWARD COMPATIBILITY CHANGE - - -