|From:||Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>|
|Subject:||Re: Restricting maximum keep segments by repslots|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Hello, this is a rebased version.
It gets a change of the meaning of monitoring value along with
In previous version, the "live" column mysteriously predicts the
necessary segments will be kept or lost by the next checkpoint
and the "distance" offered a still more mysterious value.
In this version the meaning of the two columns became clear and
- live :
true the slot have not lost necessary segments.
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.
There is a case where live = t and distance = 0. The slot is
currently having all the necessary segments but will start to
lose them at most two checkpoint passes.
NTT Open Source Software Center
|Next Message||Kyotaro HORIGUCHI||2017-10-31 09:46:22||Re: Protect syscache from bloating with negative cache entries|
|Previous Message||Robert Haas||2017-10-31 09:30:11||Re: EXPLAIN (ANALYZE, BUFFERS) reports bogus temporary buffer reads|