Re: [HACKERS] Restricting maximum keep segments by repslots
От | Kyotaro HORIGUCHI |
---|---|
Тема | Re: [HACKERS] Restricting maximum keep segments by repslots |
Дата | |
Msg-id | 20170302.095414.264042561.horiguchi.kyotaro@lab.ntt.co.jp обсуждение исходный текст |
Ответ на | Re: [HACKERS] Restricting maximum keep segments by repslots (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>) |
Ответы |
Re: [HACKERS] Restricting maximum keep segments by repslots
|
Список | pgsql-hackers |
At Wed, 1 Mar 2017 12:18:07 -0500, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote in <98538b00-42ae-6a6b-f852-50b3c937ade4@2ndquadrant.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_sizemin_wal_sizewal_write_flush_after In segmentswal_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
В списке pgsql-hackers по дате отправления: