Horton

Re: pg_ctl idempotent option

Heikki Linnakangas <hlinnakangas@vmware.com>

View thread View on postgr.es
From: Heikki Linnakangas <hlinnakangas@vmware.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>, Tom Lane <tgl@sss.pgh.pa.us>, Peter Eisentraut <peter_e@gmx.net>, pgsql-hackers@postgresql.org
Date: 2013-01-23T19:00:25Z
Lists: pgsql-hackers 
On 23.01.2013 20:56, Bruce Momjian wrote:
> On Tue, Jan 22, 2013 at 06:03:28PM +0530, Ashutosh Bapat wrote:
>> anyway, +1 for making this as default option. Going that path, would
>> we be breaking backward compatibility? There might be scripts, (being
>> already used), which depend upon the current behaviour.
>
> FYI, I have a pg_upgrade patch that relies on the old throw-an-error
> behavior.  Will there be a way to still throw an error if we make
> idempotent the default?

Could you check the status with "pg_ctl status" first, and throw an 
error if it's not what you expected?

- Heikki