Re: [HACKERS] Restricting maximum keep segments by repslots
| От | Andres Freund |
|---|---|
| Тема | Re: [HACKERS] Restricting maximum keep segments by repslots |
| Дата | |
| Msg-id | 20171106132050.6apzynxrqrzghb4r@alap3.anarazel.de обсуждение исходный текст |
| Ответ на | Re: [HACKERS] Restricting maximum keep segments by repslots (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>) |
| Ответы |
Re: [HACKERS] Restricting maximum keep segments by repslots
|
| Список | pgsql-hackers |
Hi, On 2017-10-31 18:43:10 +0900, Kyotaro HORIGUCHI wrote: > - distance: > how many bytes LSN can advance before the margin defined by > max_slot_wal_keep_size (and wal_keep_segments) is exhasuted, > or how many bytes this slot have lost xlog from restart_lsn. I don't think 'distance' is a good metric - that's going to continually change. Why not store the LSN that's available and provide a function that computes this? Or just rely on the lsn - lsn operator? - Andres -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: