database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-30 11:03:19 +03:00
Code Activity

Remove documentation of log_restartpoints setting, which is obsoleted

Browse Source 
in favor of log_checkpoints.  Fujii Masao
This commit is contained in:
Tom Lane
2009-03-05 19:50:03 +00:00
parent 08eb37da4c
commit df8684c56f
1 changed files with 2 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
doc/src/sgml/backup.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.122 2009/01/13 00:54:11 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.123 2009/03/05 19:50:03 tgl Exp $ -->
<chapter id="backup"> <chapter id="backup">
<title>Backup and Restore</title> <title>Backup and Restore</title>
@ -1198,20 +1198,6 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows
</listitem> </listitem>
</varlistentry> </varlistentry>
<varlistentry id="log-restartpoints"
xreflabel="log_restartpoints">
<term><varname>log_restartpoints</varname>
(<type>boolean</type>)
</term>
<listitem>
<para>
Specifies whether to log each restart point as it occurs. This
can be helpful to track the progress of a long recovery.
Default is <literal>false</>.
</para>
</listitem>
</varlistentry>
</variablelist> </variablelist>
</sect3> </sect3>
@ -1865,7 +1851,7 @@ if (!triggered)
backup. You can do this by running <application>pg_controldata</> backup. You can do this by running <application>pg_controldata</>
on the standby server to inspect the control file and determine the on the standby server to inspect the control file and determine the
current checkpoint WAL location, or by using the current checkpoint WAL location, or by using the
<varname>log_restartpoints</> option to print values to the server log. <varname>log_checkpoints</> option to print values to the server log.
</para> </para>
</sect2> </sect2>
</sect1> </sect1>