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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
