| From: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | peter(dot)eisentraut(at)2ndquadrant(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Restricting maximum keep segments by repslots |
| Date: | 2017-03-02 00:54:14 |
| Message-ID: | 20170302.095414.264042561.horiguchi.kyotaro@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At Wed, 1 Mar 2017 12:18:07 -0500, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote in <98538b00-42ae-6a6b-f852-50b3c937ade4(at)2ndquadrant(dot)com>
> On 2/27/17 22:27, Kyotaro HORIGUCHI wrote:
> > This patch adds a GUC to put a limit to the number of segments
> > that replication slots can keep.
>
> Please measure it in size, not in number of segments.
It was difficult to dicide which is reaaonable but I named it
after wal_keep_segments because it has the similar effect.
In bytes(or LSN)
max_wal_size
min_wal_size
wal_write_flush_after
In segments
wal_keep_segments
But surely max_slot_wal_keep_segments works to keep disk space so
bytes would be reasonable.
regards,
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2017-03-02 01:11:30 | Re: logical decoding of two-phase transactions |
| Previous Message | Kyotaro HORIGUCHI | 2017-03-02 00:43:50 | Re: Restricting maximum keep segments by repslots |