Re: allow online change primary_conninfo

Sergei Kornilov <sk@zsrv.org>

From: Sergei Kornilov <sk@zsrv.org>

To: Alvaro Herrera <alvherre@2ndquadrant.com>

Cc: Michael Paquier <michael@paquier.xyz>, Tomas Vondra <tomas.vondra@2ndquadrant.com>, Kyotaro Horiguchi <horikyota.ntt@gmail.com>, "andres@anarazel.de" <andres@anarazel.de>, "david@pgmasters.net" <david@pgmasters.net>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

Date: 2020-03-27T18:22:20Z

Lists: pgsql-hackers

Attachments

v12-0003-draft-temp-slot-name.patch (text/x-diff) patch v12-0003
v12-0002-Rework-wal_receiver_create_temp_slot-using-new-i.patch (text/x-diff) patch v12-0002
v12-0001-Allow-changing-primary_conninfo-and-primary_slot.patch (text/x-diff) patch v12-0001

Hello

In other words, patches in reverse order:
0001 will change primary_conninfo and primary_slot_name to reloadable
0002 will move wal_receiver_create_temp_slot logic to startup process (without changing to PGC_POSTMASTER)
0003 is new draft patch: wal_receiver_create_temp_slot will use the given name or generate new one.

regards, Sergei

Commits

Allow walreceiver configuration to change on reload
- 1e6148032e4d 13.0 landed