Re: [HACKERS] Restricting maximum keep segments by repslots

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

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

To: thomas.munro@enterprisedb.com

Cc: sk@zsrv.org, michael.paquier@gmail.com, andres@anarazel.de, peter.eisentraut@2ndquadrant.com, pgsql-hackers@postgresql.org

Date: 2018-01-29T10:40:23Z

Lists: pgsql-hackers

Attachments

0001-Add-WAL-releaf-vent-for-replication-slots.patch (text/x-patch)

Hello,

At Mon, 29 Jan 2018 19:26:34 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp> wrote in <20180129.192634.217484965.horiguchi.kyotaro@lab.ntt.co.jp>
> While rechecking the patch, I fixed the message issued on losing
> segments in 0001, revised the TAP test since I found that it was
> unstable.
> 
> The attached files are the correct version of the latest patch.

The name of the new function GetMinKeepSegment seems giving wrong
meaning. I renamed it to GetOlestKeepSegment.

regards,

-- 
Kyotaro Horiguchi
NTT Open Source Software Center

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