Re: allow online change primary_conninfo - Mailing list pgsql-hackers

From Sergei Kornilov
Subject Re: allow online change primary_conninfo
Date
Msg-id 3033811550437565@myt1-e20b74e6250c.qloud-c.yandex.net
Whole thread Raw
In response to Re: allow online change primary_conninfo  (Andres Freund <andres@anarazel.de>)
Responses Re: allow online change primary_conninfo  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Hi

> For one, it's not ok to just let the startup process think that the
> walreceiver failed - that'll make it change source of WAL to the next
> available method. Something we definitely do not want, as
> restore_command is very commonly slower.

Ok. This was not mentioned before Michael response yesterday. restore_command is much faster compared to database
restart,also switch to a different method was proposed few years ago by Simon Riggs in original change recovery.conf
proposal(
https://www.postgresql.org/message-id/flat/CANP8+jLO5fmfudbB1b1iw3pTdOK1HBM=xMTaRfOa5zpDVcqzew@mail.gmail.com/). I
assumedwe can start with this. Sorry for your wasted time.
 

> That'd still switch to a different method, something we do not want...

Ok, do not want means we do not want. Will try change behavior.

regards, Sergei


pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: REL_11_STABLE: dsm.c - cannot unpin a segment that is not pinned
Next
From: Thomas Munro
Date:
Subject: Re: REL_11_STABLE: dsm.c - cannot unpin a segment that is not pinned