Re: pg_archivecleanup bug - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_archivecleanup bug
Date
Msg-id 20140318181850.GD4776@momjian.us
Whole thread Raw
In response to Re: pg_archivecleanup bug  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: pg_archivecleanup bug  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: pg_archivecleanup bug  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Tue, Mar 18, 2014 at 06:11:30PM +0000, Simon Riggs wrote:
> On 18 March 2014 18:01, Bruce Momjian <bruce@momjian.us> wrote:
> > On Tue, Mar 18, 2014 at 04:17:53PM +0000, Simon Riggs wrote:
> >> > While I am not a fan of backpatching, the fact we are ignoring errors in
> >> > some critical cases seems the non-cosmetic parts should be backpatched.
> >>
> >> pg_resetxlog was not an offender here; its coding was sound.
> >>
> >> We shouldn't be discussing backpatching a patch that contains changes
> >> to coding style.
> >
> > I was going to remove the coding style changes to pg_resetxlog from the
> > backpatched portion.
> 
> Why make style changes at all? A patch with no style changes would
> mean backpatch and HEAD versions would be the same.

The old style had errno set in two places in the loop, while the new
style has it set in only one place.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + Everyone has their own god. +



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Risk Estimation WAS: Planner hints in Postgresql
Next
From: Atri Sharma
Date:
Subject: Re: Risk Estimation WAS: Planner hints in Postgresql