public inbox for [email protected]
help / color / mirror / Atom feedFrom: Daniel Gustafsson <[email protected]>
To: [email protected]
Subject: restart point vs restartpoint in the docs
Date: Tue, 2 Dec 2025 10:36:30 +0100
Message-ID: <[email protected]> (raw)
While doing something else I noticed that we have 25 uses of "restartpoint" and
three "restart point":
$ git grep -i "restartpoint[s]\?[ .,;]" doc/ | wc -l
25
$ git grep -i "restart point[s]\?[ .,;]" doc/ | wc -l
3
Any objection to applying the attached to make those three "restartpoint" to
keep the docs consistent?
--
Daniel Gustafsson
Attachments:
[application/octet-stream] restartpoint.diff (1.9K, 2-restartpoint.diff)
download | inline diff:
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 737b90736bf..405c9689bd0 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -4050,7 +4050,7 @@ include_dir 'conf.d'
(The path name is relative to the current working directory,
i.e., the cluster's data directory.)
Any <literal>%r</literal> is replaced by the name of the file containing the
- last valid restart point. That is the earliest file that must be kept
+ last valid restartpoint. That is the earliest file that must be kept
to allow a restore to be restartable, so this information can be used
to truncate the archive to just the minimum required to support
restarting from the current restore. <literal>%r</literal> is typically only
@@ -4095,7 +4095,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows
cleaning up old archived WAL files that are no longer needed by the
standby server.
Any <literal>%r</literal> is replaced by the name of the file containing the
- last valid restart point.
+ last valid restartpoint.
That is the earliest file that must be <emphasis>kept</emphasis> to allow a
restore to be restartable, and so all files earlier than <literal>%r</literal>
may be safely removed.
@@ -4139,7 +4139,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows
<varname>recovery_end_command</varname> is to provide a mechanism for cleanup
following replication or recovery.
Any <literal>%r</literal> is replaced by the name of the file containing the
- last valid restart point, like in <xref linkend="guc-archive-cleanup-command"/>.
+ last valid restartpoint, like in <xref linkend="guc-archive-cleanup-command"/>.
</para>
<para>
If the command returns a nonzero exit status then a warning log
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: restart point vs restartpoint in the docs
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox