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 dc7faead-61c4-402e-a6dc-534192833d77@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Restricting maximum keep segments by repslots  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
Responses Re: [HACKERS] Restricting maximum keep segments by repslots  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
List pgsql-hackers
On 2/27/17 23:27, Petr Jelinek wrote:
>>> WARNING:  restart LSN of replication slots is ignored by checkpoint
>>> DETAIL:  Some replication slots lose required WAL segnents to continue.
> However this is dangerous as logical replication slot does not consider
> it error when too old LSN is requested so we'd continue replication,
> hiding data loss.

In general, we would need a much more evident and strict way to discover
when this condition is hit.  Like a "full" column in
pg_stat_replication_slot, and refusing connections to the slot until it
is cleared.

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



pgsql-hackers by date:

Previous
From: Josh Soref
Date:
Subject: Re: [HACKERS] Possible spelling fixes
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Restricting maximum keep segments by repslots