Re: replication_slots usability issue - Mailing list pgsql-hackers

From Andres Freund
Subject Re: replication_slots usability issue
Date
Msg-id 20181031224802.lamhfjil7uwpfiee@alap3.anarazel.de
Whole thread Raw
In response to Re: replication_slots usability issue  (Andres Freund <andres@anarazel.de>)
Responses Re: replication_slots usability issue  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 2018-10-30 10:52:54 -0700, Andres Freund wrote:
> On 2018-10-30 11:51:09 +0900, Michael Paquier wrote:
> > On Mon, Oct 29, 2018 at 12:13:04PM -0700, Andres Freund wrote:
> > > I don't think this quite is the problem. ISTM the issue is rather that
> > > StartupReplicationSlots() *needs* to check whether wal_level > minimal,
> > > and doesn't. So you can create a slot, shutdown, change wal_level,
> > > startup. A slot exists but won't work correctly.
> > 
> > It seems to me that what we are looking for is just to complain at
> > startup if we find any slot data and if trying to start up with
> > wal_level = minimal.
> 
> Right, we really should just call CheckSlotRequirements() before doing
> so. I'll make it so, once I'm actually awake and had some coffee.

And done.  Thanks for the report JD.

- Andres


pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: PostgreSQL Limits and lack of documentation about them.
Next
From: "Nasby, Jim"
Date:
Subject: Re: PostgreSQL Limits and lack of documentation about them.