pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Restricting maximum keep segments by repslots
Date: Fri, 1 Sep 2017 23:49:21 -0400
Message-ID: <751e09c4-93e0-de57-edd2-e64c4950f5e3@2ndquadrant.com> (raw)
In-Reply-To: <20170828.183614.200480339.horiguchi.kyotaro@lab.ntt.co.jp>
References: <20170302.095414.264042561.horiguchi.kyotaro@lab.ntt.co.jp>
	<ac510b45-7805-7ccc-734c-1b38a6645f3e@2ndquadrant.com>
	<20170306.182006.172683338.horiguchi.kyotaro@lab.ntt.co.jp>
	<20170828.183614.200480339.horiguchi.kyotaro@lab.ntt.co.jp>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

I'm still concerned about how the critical situation is handled.  Your
patch just prints a warning to the log and then goes on -- doing what?
The warning rolls off the log, and then you have no idea what happened,
or how to recover.

I would like a flag in pg_replication_slots, and possibly also a
numerical column that indicates how far away from the critical point
each slot is.  That would be great for a monitoring system.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (143+ messages)  latest in thread

Message-ID: <751e09c4-93e0-de57-edd2-e64c4950f5e3@2ndquadrant.com>
Permalink:  ../751e09c4-93e0-de57-edd2-e64c4950f5e3@2ndquadrant.com/
Also on:    postgresql.org/message-id/751e09c4-93e0-de57-edd2-e64c4950f5e3@2ndquadrant.com

 · 

reply
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: peter.eisentraut@2ndquadrant.com, horiguchi.kyotaro@lab.ntt.co.jp
  Subject: Re: Restricting maximum keep segments by repslots
  In-Reply-To: <751e09c4-93e0-de57-edd2-e64c4950f5e3@2ndquadrant.com>

* 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