setting for keep_wal_segments with replication slots, postgresql 9.4 - Mailing list pgsql-admin

From John Scalia
Subject setting for keep_wal_segments with replication slots, postgresql 9.4
Date
Msg-id CABzCKRA9tsNRz2bXmMNFfgeKMKct0mn2xJpFnvPgM22CV407xw@mail.gmail.com
Whole thread Raw
Responses Re: setting for keep_wal_segments with replication slots, postgresql 9.4  (Payal Singh <payal@omniti.com>)
List pgsql-admin
Hi all,

I've been reading section 25.2.6 Replication Slots in the docs, and I'm just a little confused. This section clearly states that replication slots automates the management of WAL slots so the master will not remove them prior to receipt by all standbys. Then, the second paragraph begins "In lieu of using replication slots... use keep_wal_segments". So, if I have a primary-standby cluster using a replication slot, then what, if anything, should keep_wal_segments be set to? Should I just comment it out?

Also, if the slot is managing the storage of WAL segments, then isn't there a possibility of filling up a disk in the event of an outage? And would keep_wal_segments prevent that? This whole section just seems to be a little vague to me and like it wasn't updated cleanly since slots were envisioned.

Maybe it's just too early in the morning for me :-)
Jay

pgsql-admin by date:

Previous
From: Jorge Torralba
Date:
Subject: What am I missing? Explain row estimate wrong
Next
From: Payal Singh
Date:
Subject: Re: setting for keep_wal_segments with replication slots, postgresql 9.4