archive_command was duplicated in backup.sgml
Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.
You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:
docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t77360psql -h localhost -U postgresBuilt from patchset v1 (message #1), July 28, 2026 at 10:17 AM.
Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:
git clone --branch t77360_1 https://github.com/hackorum-dev/postgres.gitIn a checkout you already have, add the fork once:
git remote add hackorum https://github.com/hackorum-dev/postgres.gitthen, for this patchset and every later one:
git fetch hackorum t77360_1 && git checkout t77360_1Patchset v1 (message #1) is on t77360_1
Hi,
<varname>archive_command</varname> was written twice in backup.sgml.
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 8bab521718..be05a33205 100644
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -956,8 +956,7 @@ SELECT * FROM pg_backup_stop(wait_for_archive => true);
On a standby, <varname>archive_mode</varname> must be
<literal>always</literal> in order
for <function>pg_backup_stop</function> to wait.
Archiving of these files happens automatically since you have
- already configured <varname>archive_command</varname> or
<varname>archive_library</varname> or
- <varname>archive_command</varname>.
+ already configured <varname>archive_command</varname> or
<varname>archive_library</varname>.
In most cases this happens quickly, but you are advised to monitor your
archive system to ensure there are no delays.
If the archive process has fallen behind because of failures of theThis has been fixed so it is closed.
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=1334b79a359fb842d2d3cfe5b61ad4ccff8b82a4
Thank you.
2023年1月14日(土) 10:00 Noboru Saito <noborusai@gmail.com>:
Show quoted text
Hi,
<varname>archive_command</varname> was written twice in backup.sgml.diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index 8bab521718..be05a33205 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -956,8 +956,7 @@ SELECT * FROM pg_backup_stop(wait_for_archive => true); On a standby, <varname>archive_mode</varname> must be <literal>always</literal> in order for <function>pg_backup_stop</function> to wait. Archiving of these files happens automatically since you have - already configured <varname>archive_command</varname> or <varname>archive_library</varname> or - <varname>archive_command</varname>. + already configured <varname>archive_command</varname> or <varname>archive_library</varname>. In most cases this happens quickly, but you are advised to monitor your archive system to ensure there are no delays. If the archive process has fallen behind because of failures of the
Saito-san,
Oh, I didn't realize that you have aready pointed out this 1 hour
earlier than me. Sorry for this.
Best reagards,
--
Tatsuo Ishii
SRA OSS LLC
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
From: Noboru Saito <noborusai@gmail.com>
Subject: archive_command was duplicated in backup.sgml
Date: Sat, 14 Jan 2023 10:00:26 +0900
Message-ID: <CAAM3qnKYit5c_r+o5wYXZ7vZT3=pmJAU2uJmBGiBX=ffncDBMg@mail.gmail.com>
Show quoted text
Hi,
<varname>archive_command</varname> was written twice in backup.sgml.diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index 8bab521718..be05a33205 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -956,8 +956,7 @@ SELECT * FROM pg_backup_stop(wait_for_archive => true); On a standby, <varname>archive_mode</varname> must be <literal>always</literal> in order for <function>pg_backup_stop</function> to wait. Archiving of these files happens automatically since you have - already configured <varname>archive_command</varname> or <varname>archive_library</varname> or - <varname>archive_command</varname>. + already configured <varname>archive_command</varname> or <varname>archive_library</varname>. In most cases this happens quickly, but you are advised to monitor your archive system to ensure there are no delays. If the archive process has fallen behind because of failures of the