From: Sergei Kornilov <sk@zsrv.org>
To: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
To: michael.paquier@gmail.com <michael.paquier@gmail.com>
Cc: andres@anarazel.de <andres@anarazel.de>
Cc: peter.eisentraut@2ndquadrant.com <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] Restricting maximum keep segments by repslots
Date: Fri, 22 Dec 2017 15:04:20 +0300
Message-ID: <337571513944260@web55j.yandex.ru> (raw)
In-Reply-To: <20171222.150320.244267360.horiguchi.kyotaro@lab.ntt.co.jp>
References: <20171108.131431.170534842.horiguchi.kyotaro@lab.ntt.co.jp>
<20171109.173128.220115527.horiguchi.kyotaro@lab.ntt.co.jp>
<CAB7nPqS4bhSsDm_47GVjQno=iU6thx13MQVwwXXKBHQwfwwNCA@mail.gmail.com>
<20171222.150320.244267360.horiguchi.kyotaro@lab.ntt.co.jp>
Hello
I think limit wal in replication slots is useful in some cases. But first time i was confused with proposed terminology secured/insecured/broken/unknown state.
patch -p1 gives some "Stripping trailing CRs from patch" messages for me, but applied to current HEAD and builds. After little testing i understood the difference in secured/insecured/broken terminology. Secured means garantee to keep wal, insecure - wal may be deleted with next checkpoint, broken - wal already deleted.
I think, we may split "secure" to "streaming" and... hmm... "waiting"? "keeping"? - according active flag for clarify and readable "status" field.
regards, Sergei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: sk@zsrv.org, horiguchi.kyotaro@lab.ntt.co.jp, michael.paquier@gmail.com, andres@anarazel.de, peter.eisentraut@2ndquadrant.com
Subject: Re: [HACKERS] Restricting maximum keep segments by repslots
In-Reply-To: <337571513944260@web55j.yandex.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox