Re: [HACKERS] Restricting maximum keep segments by repslots

Thomas Munro <thomas.munro@enterprisedb.com>

From: Thomas Munro <thomas.munro@enterprisedb.com>

To: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>

Cc: sk@zsrv.org, Michael Paquier <michael.paquier@gmail.com>, Andres Freund <andres@anarazel.de>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Pg Hackers <pgsql-hackers@postgresql.org>

Date: 2018-01-28T22:07:31Z

Lists: pgsql-hackers

On Thu, Jan 11, 2018 at 7:59 PM, Kyotaro HORIGUCHI
<horiguchi.kyotaro@lab.ntt.co.jp> wrote:
> [new patch set]

FYI this is still broken:

test ddl                      ... FAILED

You could see that like this:

cd contrib/test_decoding
make check

-- 
Thomas Munro
http://www.enterprisedb.com

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