From 329730827848f61eb8d353d5addcbd885fa823da Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Tue, 14 Jan 2020 14:07:11 +0100 Subject: 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 Discussion: https://www.postgresql.org/message-id/CA%2Bfd4k4dM0iEPLxyVyme2RAFsn8SUgrNtBJOu81YqTY4V%2BnqZA%40mail.gmail.com --- doc/src/sgml/config.sgml | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) (limited to 'doc/src') diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 5d1c90282f9..5d45b6f7cba 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -4124,6 +4124,26 @@ ANY num_sync ( + wal_receiver_create_temp_slot (boolean) + + wal_receiver_create_temp_slot configuration parameter + + + + + Specifies whether a WAL receiver should create a temporary replication + slot on the remote instance when no permanent replication slot to use + has been configured (using ). + The default is on. The only reason to turn this off would be if the + remote instance is currently out of available replication slots. This + parameter can only be set in the postgresql.conf + file or on the server command line. Changes only take effect when the + WAL receiver process starts a new connection. + + + + wal_receiver_status_interval (integer) -- cgit v1.2.3