Re: archive modules - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: archive modules
Date
Msg-id d9d1f7fd-dd99-98f9-8aed-0e976921573b@enterprisedb.com
Whole thread Raw
In response to Re: archive modules  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: archive modules
List pgsql-hackers
On 15.09.22 00:27, Nathan Bossart wrote:
> Both archive_command and archive_library are PGC_SIGHUP, so IIUC that
> wouldn't be sufficient.  I attached a quick sketch that seems to provide
> the desired behavior.  It's nowhere near committable yet, but it
> demonstrates what I'm thinking.

What is the effect of issuing a warning like in this patch?  Would it 
just not archive anything until the configuration is fixed?  I'm not 
sure what behavior you are going for; it's a bit hard to imagine from 
just reading the patch.




pgsql-hackers by date:

Previous
From: Alena Rybakina
Date:
Subject: Re: RFC: Logging plan of the running query
Next
From: Michael Paquier
Date:
Subject: Re: Refactor backup related code (was: Is it correct to say, "invalid data in file \"%s\"", BACKUP_LABEL_FILE in do_pg_backup_stop?)