On Thu, Jan 09, 2020 at 03:14:59PM +0100, Jehan-Guillaume de Rorthais wrote:
> If you can afford that, this is the cleanest and easiest procedure you could
> find.
>
> Note that pg_basebackup need an empty PGDATA, so it will have to transfert the
> whole instance from new promoted primary to the or
On Thu, 9 Jan 2020 06:55:18 -0500
Rita wrote:
> Thanks for the response.
> I am using Postgresql 11.
> I want something simple and I have a strong preference toward using stock
> tools. After the promotion and the original master comes online, I was
> thinking of doing a pg_basebackup to sync. An
Thanks for the response.
I am using Postgresql 11.
I want something simple and I have a strong preference toward using stock
tools. After the promotion and the original master comes online, I was
thinking of doing a pg_basebackup to sync. Any thoughts about that? I had a
very hard time with pg_rewi
On Wed, Jan 08, 2020 at 11:06:28PM -0500, Rita wrote:
> I run a master and standby setup with Postgresql 11. The systems are
> identical from a hardware and software setup. If the master goes down I
> can do a pg_ctl promote on the standby and point my applications to use the
> standby (new master
I run a master and standby setup with Postgresql 11. The systems are
identical from a hardware and software setup. If the master goes down I
can do a pg_ctl promote on the standby and point my applications to use the
standby (new master).
Once the original master is online, when is an appropriate
