Re: Blank archive_command - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Blank archive_command
Date
Msg-id 4115560.1642433537@sss.pgh.pa.us
Whole thread Raw
In response to Re: Blank archive_command  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: Blank archive_command
List pgsql-hackers
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.

            regards, tom lane



pgsql-hackers by date:

Previous
From: "houzj.fnst@fujitsu.com"
Date:
Subject: RE: row filtering for logical replication
Next
From: Bharath Rupireddy
Date:
Subject: Re: Blank archive_command