Re: bug in on_error_rollback !? - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: bug in on_error_rollback !?
Date
Msg-id 9285f03a09691f7ba550f0987118bb23@biglumber.com
Whole thread Raw
In response to Re: bug in on_error_rollback !?  ("Andrew Dunstan" <andrew@dunslane.net>)
Responses Re: bug in on_error_rollback !?  (Robert Treat <xzilla@users.sourceforge.net>)
Re: bug in on_error_rollback !?  ("Jim C. Nasby" <jim@nasby.net>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> This is documented clearly on the psql man page, so it is simply not a
> bug, and changing this would probably break lots of legacy scripts.

In a general sense, perhaps, but in this *particular* case, I don't
see what harm allowing "\set on_error_rollback" would be: it certainly
won't break any existing scripts. I wrote this feature (but someone else
chose the name!) and I still occasionally write it lowercase and wonder
why it isn't working. :)

Perhaps even allowing all of the \set commands to be case-insensitive
may be a good idea?

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200610270914
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8

-----BEGIN PGP SIGNATURE-----

iD8DBQFFQgawvJuQZxSWSsgRAvBKAKDb4gcpRsjpbxo7SKJwmu5y7Bo48QCeIMao
DZFuEIPJaPNyv/TRGNH6shc=
=/n5U
-----END PGP SIGNATURE-----




pgsql-hackers by date:

Previous
From: Dave Cramer
Date:
Subject: Re: 8.1-407 JDBC driver issues
Next
From: Tom Lane
Date:
Subject: Re: Deadlock with pg_dump?