Re: Continue transactions after errors in psql - Mailing list pgsql-patches

From Tom Lane
Subject Re: Continue transactions after errors in psql
Date
Msg-id 3703.1110266478@sss.pgh.pa.us
Whole thread Raw
In response to Re: Continue transactions after errors in psql  ("Michael Paesold" <mpaesold@gmx.at>)
Responses Re: Continue transactions after errors in psql
Re: Continue transactions after errors in psql
List pgsql-patches
"Michael Paesold" <mpaesold@gmx.at> 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.

            regards, tom lane

pgsql-patches by date:

Previous
From: Neil Conway
Date:
Subject: Re: Display Pg buffer cache (WIP)
Next
From: Mark Kirkwood
Date:
Subject: Re: Display Pg buffer cache (WIP)