Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: Why --backup-and-modify-in-place in perltidy config?
Date
Msg-id 19914.1471285423@sss.pgh.pa.us
Whole thread Raw
In response to Re: Why --backup-and-modify-in-place in perltidy config?  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Why --backup-and-modify-in-place in perltidy config?  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Tree view 
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.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Shay Rojansky
Date:
Subject: Re: Slowness of extended protocol
Next
From: Tom Lane
Date:
Subject: Let's get rid of the separate minor version numbers for shlibs