Re: Restricting maximum keep segments by repslots

Andres Freund <andres@anarazel.de>

From: Andres Freund <andres@anarazel.de>

To: Michael Paquier <michael.paquier@gmail.com>

Cc: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>, PostgreSQL mailing lists <pgsql-hackers@postgresql.org>

Date: 2017-03-01T16:06:10Z

Lists: pgsql-hackers

Hi,

On 2017-02-28 12:42:32 +0900, Michael Paquier wrote:
> Please no. Replication slots are designed the current way because we
> don't want to have to use something like wal_keep_segments as it is a
> wart, and this applies as well for replication slots in my opinion.

I think a per-slot option to limit the amount of retention would make
sense.

- Andres

Commits

Save slot's restart_lsn when invalidated due to size
- 12e52ba5a76e 13.0 landed
- 0188bb82531f 14.0 landed
Fix checkpoint signalling
- 1816a1c6ffe4 13.0 landed
Check slot->restart_lsn validity in a few more places
- d0abe78d8427 13.0 landed
Allow users to limit storage reserved by replication slots
- c6550776394e 13.0 landed
Remove header noise from test_decoding test
- 69360b34589b 13.0 landed
Rework WAL-reading supporting structs
- 709d003fbd98 13.0 cited
Flip argument order in XLogSegNoOffsetToRecPtr
- a22445ff0be2 12.0 cited