From: Tom Lane <tgl@sss.pgh.pa.us>
To: andrew.lozovsky@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18666: Standby cluster does not start after building from Primary cluster.
Date: Mon, 21 Oct 2024 10:20:12 -0400
Message-ID: <1551043.1729520412@sss.pgh.pa.us> (raw)
In-Reply-To: <18666-ac3af3f657ead7e2@postgresql.org>
References: <18666-ac3af3f657ead7e2@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> Standby cluster does not start after building from Primary cluster.
I think your archiving setup is broken:
> archive_command = 'cp %p /dev/null'
> ...
> restore_command = 'cp /opt/archivelog/%f %p'
BTW, "cp" is widely regarded as not being safe enough for production
archiving, because it doesn't fsync. But this archive_command
isn't even trying. So it's not surprising if there's not enough WAL
to recover from.
regards, tom lane
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: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, andrew.lozovsky@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18666: Standby cluster does not start after building from Primary cluster.
In-Reply-To: <1551043.1729520412@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox