From: | Greg Stark <stark(at)mit(dot)edu> |
---|---|
To: | Sergei Kornilov <sk(at)zsrv(dot)org> |
Cc: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, "michael(dot)paquier(at)gmail(dot)com" <michael(dot)paquier(at)gmail(dot)com>, "andres(at)anarazel(dot)de" <andres(at)anarazel(dot)de>, "peter(dot)eisentraut(at)2ndquadrant(dot)com" <peter(dot)eisentraut(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] Restricting maximum keep segments by repslots |
Date: | 2018-01-11 13:56:14 |
Message-ID: | CAM-w4HOVYZkCbCdFt8N8zwAAcuETFimwOB_Db+jgFajn-iYHEQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11 January 2018 at 09:55, Sergei Kornilov <sk(at)zsrv(dot)org> wrote:
> if (active_pid != 0)
> status = "streaming";
> else
> status = "keeping";
Perhaps "idle" by analogy to a pg_stat_activity entry for a backend
that's connected but not doing anything.
> status = "may_lost";
Perhaps "stale" or "expired"?
Is this patch in bike-shed territory? Are there any questions about
whether we want the basic shape to look like this?
Fwiw I think there's a real need for this feature so I would like to
get it in for Postgres 11.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2018-01-11 14:02:46 | Re: [HACKERS] Early locking option to parallel backup |
Previous Message | Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?= | 2018-01-11 12:54:48 | Re: numeric regression test passes, but why? |