Re: [HACKERS] Restricting maximum keep segments by repslots

From: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
To: thomas(dot)munro(at)enterprisedb(dot)com
Cc: sk(at)zsrv(dot)org, michael(dot)paquier(at)gmail(dot)com, andres(at)anarazel(dot)de, peter(dot)eisentraut(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Restricting maximum keep segments by repslots
Date: 2018-01-29 10:40:23
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


At Mon, 29 Jan 2018 19:26:34 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> wrote in <20180129(dot)192634(dot)217484965(dot)horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)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.


Kyotaro Horiguchi
NTT Open Source Software Center

Attachment Content-Type Size
0001-Add-WAL-releaf-vent-for-replication-slots.patch text/x-patch 6.9 KB
0002-Add-monitoring-aid-for-max_replication_slots.patch text/x-patch 9.4 KB
0003-TAP-test-for-the-slot-limit-feature.patch text/x-patch 5.3 KB
0004-Documentation-for-slot-limit-feature.patch text/x-patch 5.2 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Yugo Nagata 2018-01-29 11:25:50 Re: [HACKERS] [PATCH] Lockable views
Previous Message Simon Riggs 2018-01-29 10:38:22 Re: Logical Decoding and HeapTupleSatisfiesVacuum assumptions