Re: Why --backup-and-modify-in-place in perltidy config? - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Why --backup-and-modify-in-place in perltidy config?
Date
Msg-id 57B29467.4080501@dunslane.net
Whole thread Raw
In response to Re: Why --backup-and-modify-in-place in perltidy config?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Why --backup-and-modify-in-place in perltidy config?  (Gavin Flower <GavinFlower@archidevsys.co.nz>)
List pgsql-hackers

On 08/15/2016 02:23 PM, Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>> On 08/15/2016 10:19 AM, Tom Lane wrote:
>>> Andrew Dunstan <andrew@dunslane.net> writes:
>>>> We should probably specify -bext='/', which would cause the backup files
>>>> to be deleted unless an error occurred.
>>> Really?  That seems a bit magic, and it's certainly undocumented.
>> We must be using different versions.
> Hmm ... I'm using the RHEL6 version, which claims to be v20090616,
> which is what pgindent/README says to use.


Ah. I have Fedora 22's v20140711. 2009 seems a bit ancient :-) Anyway, 
what you've done seems fine.

cheers

andrew




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: anyelement -> anyrange
Next
From: Amit Langote
Date:
Subject: Re: Fix comment in ATExecValidateConstraint