Re: Continue transactions after errors in psql
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Michael Paesold" <mpaesold@gmx.at>
Cc: "Greg Sabino Mullane" <greg@turnstep.com>, pgsql-patches@postgresql.org
Date: 2005-03-08T07:21:18Z
Lists: pgsql-hackers
"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