Re: [PATCHES] Continue transactions after errors in psql - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: [PATCHES] Continue transactions after errors in psql
Date
Msg-id e6a9b1c3b6ef8237abdcca5e806c3595@biglumber.com
Whole thread Raw
In response to Re: [PATCHES] Continue transactions after errors in psql  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [PATCHES] Continue transactions after errors in psql
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

     

     
To reiterate my opinion, I think the behavior should be the same
for interactive and non-interactive sessions. Not only will it
prevent nasty surprises, but unless we make a third 'setting',
there will be no way to enable this in non-interactive scripts,
which is something that I would want to be able to do.

     
I don't buy the "but what if I set it in .psqlrc and forget" argument.
That could be applied to a lot of things you could put in there. This
setting defaults to "off" and must be explicitly enabled. I'd be okay
with a "smart" mode that explicitly enables the interactive/non-interactive
split.

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

iD8DBQFCbilxvJuQZxSWSsgRAgf8AJ9/NcsU/5A0V9isGvQy4sjba/aukgCgoFbp
otSb0vVLfnL7mIt99rA4Piw=
=1vVP
-----END PGP SIGNATURE-----



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: bitmapscan test, no success, bs is not faster
Next
From: Pavel Stehule
Date:
Subject: Re: bitmapscan test, no success, again