On Mon, Jan 17, 2022 at 9:02 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> writes:
> > However, a reasonable thing to do is to
> > emit a WARNING or ERROR-out when archive_command is set to null in
> > it's check_archive_command when archive_mode is on?
>
> We have been burned badly in the past by attempts to do that sort of
> thing (ie, make behavior that's conditional on combinations of GUC
> settings). There tends to be collateral damage along the lines of
> "certain orders of operations stop working". I'm not really eager
> to open that can of worms here.
+1 to 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.
Regards,
Bharath Rupireddy.