Re: [HACKERS] Restricting maximum keep segments by repslots - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Restricting maximum keep segments by repslots
Date
Msg-id 751e09c4-93e0-de57-edd2-e64c4950f5e3@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Restricting maximum keep segments by repslots  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Responses Re: [HACKERS] Restricting maximum keep segments by repslots  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
List pgsql-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



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: [HACKERS] Secondary index access optimizations
Next
From: Pavel Stehule
Date:
Subject: [HACKERS] configure issue - warnings sort: No such file or directory