On Mon, Jan 17, 2022 at 9:05 PM Bharath Rupireddy
<bharath.rupireddyforpostgres@gmail.com> wrote:
>
> +1 to not create any GUC setting dependencies. Let's leave the
> responsibility of setting appropriate archive_command to the archiving
> handlers outside postgres. FWIW, having a note in the archive_command
> GUC definition in the docs might help to some extent.
On further search, the documentation says the following which is enough IMO:
This parameter can only be set in the postgresql.conf file or on the
server command line. It is ignored unless archive_mode was enabled at
server start. If archive_command is an empty string (the default)
while archive_mode is enabled, WAL archiving is temporarily disabled,
but the server continues to accumulate WAL segment files in the
expectation that a command will soon be provided. Setting
archive_command to a command that does nothing but return true, e.g.,
/bin/true (REM on Windows), effectively disables archiving, but also
breaks the chain of WAL files needed for archive recovery, so it
should only be used in unusual circumstances.
https://www.postgresql.org/docs/devel/runtime-config-wal.html#GUC-ARCHIVE-COMMAND
Regards,
Bharath Rupireddy.