| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Thom Brown <thom(at)linux(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Blank archive_command |
| Date: | 2022-01-17 15:32:17 |
| Message-ID: | 4115560.1642433537@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2022-01-17 15:35:59 | Re: Blank archive_command |
| Previous Message | houzj.fnst@fujitsu.com | 2022-01-17 15:30:55 | RE: row filtering for logical replication |