Commit 479ee1b9 authored by Simon Riggs's avatar Simon Riggs

Centralise release note items related to recovery and replication

parent 35d2a660
...@@ -526,32 +526,6 @@ ...@@ -526,32 +526,6 @@
</para> </para>
</listitem> </listitem>
<listitem>
<para>
Add the <link
linkend="monitoring-stats-views-table"><structname>pg_stat_database_conflicts</></link>
system view to show queries that have been canceled and the
reason (Magnus Hagander)
</para>
<para>
Cancelations can occur because of dropped tablespaces, lock
timeouts, old snapshots, pinned buffers, and deadlocks.
</para>
</listitem>
<listitem>
<para>
Add a <literal>conflicts</> count to <link
linkend="monitoring-stats-views-table"><structname>pg_stat_database</></link>
(Magnus Hagander)
</para>
<para>
This is the number of conflicts that occurred in the database.
</para>
</listitem>
<listitem> <listitem>
<para> <para>
Add record of last reset in database and background writer-level Add record of last reset in database and background writer-level
...@@ -603,26 +577,10 @@ ...@@ -603,26 +577,10 @@
</para> </para>
</listitem> </listitem>
<listitem>
<para>
Add <link
linkend="guc-restart-after-crash"><varname>restart_after_crash</></link>
which disables server restart after a backend crash (Robert
Haas)
</para>
<para>
This is designed for cluster managers that want to control
restarts.
</para>
</listitem>
<listitem> <listitem>
<para> <para>
Increase the maximum values for Increase the maximum values for
<link linkend="guc-deadlock-timeout"><varname>deadlock_timeout</varname></link>, <link linkend="guc-deadlock-timeout"><varname>deadlock_timeout</varname></link>,
<link linkend="guc-max-standby-archive-delay"><varname>max_standby_archive_delay</varname></link>,
<link linkend="guc-max-standby-streaming-delay"><varname>max_standby_streaming_delay</varname></link>,
<link linkend="guc-log-min-duration-statement"><varname>log_min_duration_statement</varname></link>, and <link linkend="guc-log-min-duration-statement"><varname>log_min_duration_statement</varname></link>, and
<link linkend="guc-log-autovacuum-min-duration"><varname>log_autovacuum_min_duration</varname></link>. <link linkend="guc-log-autovacuum-min-duration"><varname>log_autovacuum_min_duration</varname></link>.
</para> </para>
...@@ -640,6 +598,9 @@ ...@@ -640,6 +598,9 @@
</sect3> </sect3>
<sect3> <sect3>
<title>Replication and Recovery</title>
<sect4>
<title>Streaming Replication and Continuous Archiving</title> <title>Streaming Replication and Continuous Archiving</title>
<itemizedlist> <itemizedlist>
...@@ -665,20 +626,7 @@ ...@@ -665,20 +626,7 @@
<listitem> <listitem>
<para> <para>
Add variable <link Add protocol support for sending file system backups to standbys using
linkend="guc-hot-standby-feedback"><varname>hot_standby_feedback</></link>
to enable standbys to postpone cleanup of old row versions on the
primary (Simon Riggs)
</para>
<para>
This helps avoid cancelling long-running queries on the standby.
</para>
</listitem>
<listitem>
<para>
Add support for sending file system backups to standbys using
the streaming replication network connection (Magnus Hagander, the streaming replication network connection (Magnus Hagander,
Heikki Linnakangas) Heikki Linnakangas)
</para> </para>
...@@ -727,8 +675,10 @@ ...@@ -727,8 +675,10 @@
</itemizedlist> </itemizedlist>
</sect4>
<sect4> <sect4>
<title>Monitoring</title> <title>Replication Monitoring</title>
<itemizedlist> <itemizedlist>
...@@ -762,6 +712,80 @@ ...@@ -762,6 +712,80 @@
</sect4> </sect4>
<sect4>
<title>Hot Standby</title>
<itemizedlist>
<listitem>
<para>
Add variable <link
linkend="guc-hot-standby-feedback"><varname>hot_standby_feedback</></link>
to enable standbys to postpone cleanup of old row versions on the
primary (Simon Riggs)
</para>
<para>
This helps avoid cancelling long-running queries on the standby.
</para>
</listitem>
<listitem>
<para>
Add the <link
linkend="monitoring-stats-views-table"><structname>pg_stat_database_conflicts</></link>
system view to show queries that have been canceled and the
reason (Magnus Hagander)
</para>
<para>
Cancelations can occur because of dropped tablespaces, lock
timeouts, old snapshots, pinned buffers, and deadlocks.
</para>
</listitem>
<listitem>
<para>
Add a <literal>conflicts</> count to <link
linkend="monitoring-stats-views-table"><structname>pg_stat_database</></link>
(Magnus Hagander)
</para>
<para>
This is the number of conflicts that occurred in the database.
</para>
</listitem>
<listitem>
<para>
Increase the maximum values for
<link linkend="guc-max-standby-archive-delay"><varname>max_standby_archive_delay</varname></link> and
<link linkend="guc-max-standby-streaming-delay"><varname>max_standby_streaming_delay</varname></link>.
</para>
<para>
The maximum value for each of these parameters was previously
only about 35 minutes. Much larger values are now allowed.
</para>
</listitem>
<listitem>
<para>
Add <link
linkend="errcodes-table"><literal>ERRCODE_T_R_DATABASE_DROPPED</></link>
error code to report recovery conflicts due to dropped databases
(Tatsuo Ishii)
</para>
<para>
This is useful for connection pooling software.
</para>
</listitem>
</itemizedlist>
</sect4>
<sect4> <sect4>
<title>Recovery Control</title> <title>Recovery Control</title>
...@@ -783,6 +807,19 @@ ...@@ -783,6 +807,19 @@
</para> </para>
</listitem> </listitem>
<listitem>
<para>
Add <filename>recovery.conf</> setting <link
linkend="pause-at-recovery-target"><varname>pause_at_recovery_target</></link>
to pause recovery at target (Simon Riggs)
</para>
<para>
This allows a recovery server to be queried to check if the
recovery point is the one desired.
</para>
</listitem>
<listitem> <listitem>
<para> <para>
Add the ability to create named restore points using <link Add the ability to create named restore points using <link
...@@ -799,26 +836,27 @@ ...@@ -799,26 +836,27 @@
<listitem> <listitem>
<para> <para>
Add <filename>recovery.conf</> setting <link Allow standby recovery to switch to a new timeline automatically
linkend="pause-at-recovery-target"><varname>pause_at_recovery_target</></link> (Heikki Linnakangas)
to pause recovery at target (Simon Riggs)
</para> </para>
<para> <para>
This allows a recovery server to be queried to check if the Now standby servers scan the archive directory for new
recovery point is the one desired. timelines periodically.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Allow standby recovery to switch to a new timeline automatically Add <link
(Heikki Linnakangas) linkend="guc-restart-after-crash"><varname>restart_after_crash</></link>
which disables server restart after a backend crash (Robert
Haas)
</para> </para>
<para> <para>
Now standby servers scan the archive directory for new This allows external cluster management software to take control
timelines periodically. of whether servers restart or not.
</para> </para>
</listitem> </listitem>
...@@ -1559,19 +1597,6 @@ ...@@ -1559,19 +1597,6 @@
</para> </para>
</listitem> </listitem>
<listitem>
<para>
Add <link
linkend="errcodes-table"><literal>ERRCODE_T_R_DATABASE_DROPPED</></link>
error code to report recovery conflicts due to dropped databases
(Tatsuo Ishii)
</para>
<para>
This is useful for connection pooling software.
</para>
</listitem>
</itemizedlist> </itemizedlist>
</sect4> </sect4>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment