From: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | pgsql-patches(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Continue transactions after errors in psql |
Date: | 2005-04-26 11:43:31 |
Message-ID: | e6a9b1c3b6ef8237abdcca5e806c3595@biglumber.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
-----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(at)turnstep(dot)com
PGP Key: 0x14964AC8 200504260737
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iD8DBQFCbilxvJuQZxSWSsgRAgf8AJ9/NcsU/5A0V9isGvQy4sjba/aukgCgoFbp
otSb0vVLfnL7mIt99rA4Piw=
=1vVP
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2005-04-26 12:05:59 | Re: bitmapscan test, no success, again |
Previous Message | Pavel Stehule | 2005-04-26 11:20:38 | bitmapscan test, no success, bs is not faster |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paesold | 2005-04-26 12:22:03 | Re: [HACKERS] Continue transactions after errors in psql |
Previous Message | Mark Kirkwood | 2005-04-26 05:54:34 | Re: [PATCHES] Continue transactions after errors in psql |