| From: | Flavio Henrique Araque Gurgel <fhagur(at)gmail(dot)com> |
|---|---|
| To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
| Cc: | Amine Tengilimoglu <aminetengilimoglu(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: recovery.conf changes whitout restart |
| Date: | 2019-03-14 10:09:27 |
| Message-ID: | CAGHTAeMRfjCKxdLk_ODBLryorejs1iRjG4+iqZOEfodYsASsvg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> Le jeu. 14 mars 2019 à 09:13, Amine Tengilimoglu <aminetengilimoglu(at)gmail(dot)com> a écrit :
>>
>> Hi all;
>>
>> Is there any way that have effect primary conn info changes whitout restart in pg?
>> I want to keep going after change the primary conn info in recovery.conf. But we need to restart it...Is there any way to do it?
>>
>
> No, you have to restart PostgreSQL.
One thing I do in production is to use a DNS CNAME to point to the
desired origin, so I can change the CNAME destination and just drop
the old connection, standby PostgreSQL will catchup in the new otigin
without restart. Create the replication slot beforehand in the new
origin is useful and, obviously, do not forget to drop it in the old
one.
Flavio Gurgel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amine Tengilimoglu | 2019-03-15 07:21:01 | Re: recovery.conf changes whitout restart |
| Previous Message | Guillaume Lelarge | 2019-03-14 09:42:41 | Re: recovery.conf changes whitout restart |