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 CAB7nPqQimr+8LyFqiJh18Efm00pVwbuq1E-WHe3W_wYABdhhDA@mail.gmail.com
Whole thread Raw
In response to Re: Potential data loss of 2PC files  ("Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>)
List pgsql-hackers
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.
Inaddition, keeping code differences as few as possible would make it easier for committers to apply other bug fixes to
allversions.
 

The patch of HEAD applies cleanly on REL9_6_STABLE, further down it
needs some work but not much either. I am fine to produce those
patches should there be any need to.
-- 
Michael



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Use $ parameters as replacement characters for pg_stat_statements
Next
From: Lukas Fittl
Date:
Subject: Re: [PATCH] Use $ parameters as replacement characters for pg_stat_statements