| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Sergei Kornilov <sk(at)zsrv(dot)org>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, "andres(at)anarazel(dot)de" <andres(at)anarazel(dot)de>, "david(at)pgmasters(dot)net" <david(at)pgmasters(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: allow online change primary_conninfo |
| Date: | 2020-04-01 14:03:05 |
| Message-ID: | 4b1bfe72-43ab-60ca-5b29-afc23f1726e7@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-03-28 11:49, Sergei Kornilov wrote:
> I attached updated patch: walreceiver will use configured primary_slot_name as temporary slot name if wal_receiver_create_temp_slot is enabled.
The original setup worked consistently with pg_basebackup. In
pg_basebackup, if you specify -S/--slot, then it uses a permanent slot
with the given name. This is the same behavior as primary_slot_name has
now. We should be careful that we don't create two sets of
options/settings that look similar but combine in different ways.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2020-04-01 14:09:44 | Re: Commitfest 2020-03 Now in Progress |
| Previous Message | Andres Freund | 2020-04-01 14:01:28 | Re: snapshot too old issues, first around wraparound and then more. |