Skip site navigation (1) Skip section navigation (2)

Re: bug in on_error_rollback !?

From: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: bug in on_error_rollback !?
Date: 2006-10-27 13:19:25
Message-ID: 9285f03a09691f7ba550f0987118bb23@biglumber.com (view raw or flat)
Thread:
Lists: 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(at)turnstep(dot)com
PGP Key: 0x14964AC8 200610270914
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8

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

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



In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2006-10-27 13:47:44
Subject: Re: Deadlock with pg_dump?
Previous:From: Dave CramerDate: 2006-10-27 11:35:59
Subject: Re: 8.1-407 JDBC driver issues

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group