Tom Lane wrote:
> "Michael Paesold" <[EMAIL PROTECTED]> writes:
> > I do think so. In it's current state, would you yourself put \reseterror in
> > your .psqlrc? Or even an /etc/psqlrc?
> > It would break all my scripts that must either succeed or fail -- now they
> > will produce garbage in my databases when something goes wrong!
> This is sounding a whole lot like the concerns that prompted us to
> reject server-side autocommit a little while ago.
> The problem with rejiggering error-handling behavior is that you *will*
> break existing code, on a rather fundamental level, and it's not even
> obvious that it's broken until after things have gone badly wrong.
> I don't have a good solution, but I do think that you need to set things
> up so that an application or script must invoke the new behavior
> explicitly. Hidden defaults that silently change such behavior look
> like land mines waiting to be stepped on.
Right, this is off by default. We might be able to make it on by
default if we have it enabled only for interactive psql's. We need to
Bruce Momjian | http://candle.pha.pa.us
email@example.com | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly