Re: [HACKERS] replication_slot_catalog_xmin not explicitlyinitialized when creating procArray - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] replication_slot_catalog_xmin not explicitlyinitialized when creating procArray
Date
Msg-id cf7c5c92-f7a9-1eef-46d5-13db96089c6e@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] replication_slot_catalog_xmin not explicitlyinitialized when creating procArray  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
On 7/9/17 21:23, Masahiko Sawada wrote:
> On Sat, Jul 8, 2017 at 2:19 AM, Wong, Yi Wen <yiwong@amazon.com> wrote:
>> replication_slot_catalog_xmin is not explictly initialized to
>> InvalidTransactionId.

> Thank you for the patch. This change makes sense to me.

Committed and backpatched

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



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] pgbench: Skipping the creating primary keys after initialization
Next
From: Amit Langote
Date:
Subject: Re: [HACKERS] expanding inheritance in partition bound order