Re: Non-reserved replication slots and slot advancing - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Non-reserved replication slots and slot advancing
Date
Msg-id 20180703172350.hh3ky5idcqvayfs6@alvherre.pgsql
Whole thread Raw
In response to Re: Non-reserved replication slots and slot advancing  (Andres Freund <andres@anarazel.de>)
Responses Re: Non-reserved replication slots and slot advancing  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On 2018-Jul-03, Andres Freund wrote:

> I'm not clear to why this is a problem? Seems like either behaviour can
> be argued for. I don't really have an opinion either way. I'd just
> remove the item from the open items list, I don't think we need to hold
> up the release for it?

After reading this more carefully, isn't the problem that as soon as you
get a slot into the 0/1 restart_lsn state, WAL recycling/deletion no
longer happens?  That does sound like a bad thing to me.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Failed assertion due to procedure created with SECURITY DEFINERoption
Next
From: Andres Freund
Date:
Subject: Re: Non-reserved replication slots and slot advancing