From: | Amine Tengilimoglu <aminetengilimoglu(at)gmail(dot)com> |
---|---|
To: | Flavio Henrique Araque Gurgel <fhagur(at)gmail(dot)com> |
Cc: | Guillaume Lelarge <guillaume(at)lelarge(dot)info>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: recovery.conf changes whitout restart |
Date: | 2019-03-15 07:21:01 |
Message-ID: | CADTdw-yn0eq9JOQcMc1fsSrt_fTWLXPhiO+Gpgu6k6bPbgPLdQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Ok. Thank you for your answers.
Flavio Henrique Araque Gurgel <fhagur(at)gmail(dot)com>, 14 Mar 2019 Per, 13:09
tarihinde şunu yazdı:
> > 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 | wambacher | 2019-03-18 08:50:11 | Re: Can't stop pgAdmin4 server process |
Previous Message | Flavio Henrique Araque Gurgel | 2019-03-14 10:09:27 | Re: recovery.conf changes whitout restart |