walreceiver uses a temporary replication slot by default
Peter Eisentraut <peter@eisentraut.org>
walreceiver uses a temporary replication slot by default If no permanent replication slot is configured using primary_slot_name, the walreceiver now creates and uses a temporary replication slot. A new setting wal_receiver_create_temp_slot can be used to disable this behavior, for example, if the remote instance is out of replication slots. Reviewed-by: Masahiko Sawada <masahiko.sawada@2ndquadrant.com> Discussion: https://www.postgresql.org/message-id/CA%2Bfd4k4dM0iEPLxyVyme2RAFsn8SUgrNtBJOu81YqTY4V%2BnqZA%40mail.gmail.com
Files
| Path | Change | +/− |
|---|---|---|
| doc/src/sgml/config.sgml | modified | +20 −0 |
| src/backend/replication/libpqwalreceiver/libpqwalreceiver.c | modified | +4 −0 |
| src/backend/replication/walreceiver.c | modified | +41 −0 |
| src/backend/utils/misc/guc.c | modified | +9 −0 |
| src/backend/utils/misc/postgresql.conf.sample | modified | +1 −0 |
| src/include/replication/walreceiver.h | modified | +7 −0 |
Documentation touched
Discussion
- base backup client as auxiliary backend process 39 messages · 2019-06-29 → 2020-03-28