Re: BUG #14228: replication slot catalog_xmin not cleared on slot reuse - Mailing list pgsql-bugs

From Andres Freund
Subject Re: BUG #14228: replication slot catalog_xmin not cleared on slot reuse
Date
Msg-id 20160817202338.gtdm25nq3zp4i4ul@alap3.anarazel.de
Whole thread Raw
In response to Re: BUG #14228: replication slot catalog_xmin not cleared on slot reuse  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-bugs
On 2016-07-28 14:22:29 +0900, Michael Paquier wrote:
> On Thu, Jul 28, 2016 at 9:24 AM, Andres Freund <andres@anarazel.de> wrote:
> > I think it'd be better if we explicitly zeroed .data - that way the
> > likelihood of future bugs of the same ilk is smaller.
>
> Okay, I have spent some time looking at all the fields here, and their
> significance before reaching this code path in ReplicationSlotCreate,
> but did not find any hole if slot->data is zeroed. So here is an
> updated patch. You could get rid of all the field initializations I
> have done for slot->data, but I think that's cheap to keep them.

Pushed without the additional initializations - they're imo more
confusing than helpful - and with some more reordering to match the
struct order.

Regards,

Andres

pgsql-bugs by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file
Next
From: Andres Freund
Date:
Subject: Re: BUG #14150: Attempted to delete invisible tuple