[ADMIN] switching replication from standard asynch to slots - Mailing list pgsql-admin

From Mike Broers
Subject [ADMIN] switching replication from standard asynch to slots
Date
Msg-id CAB9893jPC=bPS9JatNZ8U4QjPFC1K3PZfaEt0kKgjWAE=kY+VA@mail.gmail.com
Whole thread Raw
Responses Re: [ADMIN] switching replication from standard asynch to slots  (Vladimir Borodin <root@simply.name>)
List pgsql-admin
I have a few production environments that use vanilla streaming replication.  (9.5 and 9.6)

I'm curious if I can create the replication slot on the primary host, shutdown postgres on the secondary replica, update the recovery.conf to include the primary_slot_name, and restart postgres on the replica to effectively 'switch' over to use the slot for streaming without repriming with a fresh pg_basebackup.  

Also curious if I get into a pickle because of limits in pgsql_xlog disk space if I can just shut down the replica, remove the slot information, and do whatever cleanup is required on the primary and restart the replica with the slot information removed from the recovery.conf and go back to vanilla streaming replication without repriming.

Anyone do this kind of slot/streaming switcheroo?

Mike


pgsql-admin by date:

Previous
From: hubert depesz lubaczewski
Date:
Subject: Re: [ADMIN] change pid/gid
Next
From: Sreekanth Palluru
Date:
Subject: Re: [ADMIN] Would like to below scenario is possible for gettingpage/block corruption