Hello Michael
Thank you, i understand your opinion.
I really tried to find a discussion about reload recovery.conf (or walreceiver
conninfo changing and similar stuff), not about GUC.
regards, Sergei
On Fri, May 04, 2018 at 05:19:26PM +0300, Sergei Kornilov wrote:
> I did not find previous discussions.
There have been a lot of discussions across the years about switching
recovery parameters to use the GUC infrastructure, please see those
two ones:
https://www.postgresql.org/message-id/CABUevEy
Hello all
I want propose patch to make possible change primary_conninfo,
primary_slot_name, restore_command and trigger_file in recovery.conf without
restart postgresql.
Startup process will reread recovery.conf on SIGHUP.
My primary usecase is postgresql cluster with streaming replication. When