Re: Potential data loss of 2PC files - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Potential data loss of 2PC files
Date
Msg-id CAB7nPqTBG0=CNUwAOu5EVmzkP4MFOsRc5Q2ggVUW1yeoFme4ww@mail.gmail.com
Whole thread Raw
In response to [HACKERS] Potential data loss of 2PC files  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Tue, Mar 28, 2017 at 9:37 AM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> On Tue, Mar 28, 2017 at 8:38 AM, Tsunakawa, Takayuki
> <tsunakawa.takay@jp.fujitsu.com> wrote:
>> From: pgsql-hackers-owner@postgresql.org
>>> [mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of Michael Paquier
>>> Do you think that this qualifies as a bug fix for a backpatch? I would think
>>> so, but I would not mind waiting for some dust to be on it before considering
>>> applying that on back-branches. Thoughts from others?
>>
>> I think so, too.  As change from rename() to durable_rename() was applied to all releases, maybe we can follow that.
In addition, keeping code differences as few as possible would make it easier for committers to apply other bug fixes
toall versions.
 
>
> The patch of HEAD applies cleanly on REL9_6_STABLE,

Actually that's not correct as well as pg_clog has been renamed to
pg_xact. Let's be careful here.
-- 
Michael



pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: logical replication launcher crash on buildfarm
Next
From: Petr Jelinek
Date:
Subject: Re: logical replication launcher crash on buildfarm