-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/27/06 08:41, Alexander Staubo wrote:
> On Oct 27, 2006, at 14:56 , Ron Johnson wrote:
>
>>> I think you completely missed that I am recommending using '\set
>>> ON_ERROR_ROLLBACK on' in psql.
>>>
>>> Please refer to my previous post and see the effect of the following
>>> line:
>>>
>>> postgres=# \set ON_ERROR_ROLLBACK on
>>
>> But I do *not* want my whole transaction to roll back!!
>
> That is not what is happening. From the documentation:
>
>> ON_ERROR_ROLLBACK
>> When on, if a statement in a transaction block generates an error, the
>> error is ignored and the transaction continues. When interactive, such
That'll teach me not to assume what a statement means.
>> errors are only ignored in interactive sessions, and not when reading
>> script files.
Hmmm.
I guess COPY will fail also, instead of throwing a warning and
continuing.
>> When off (the default), a statement in a transaction
>> block that generates an error aborts the entire transaction. The
>> on_error_rollback-on mode works by issuing an implicit SAVEPOINT for
>> you, just before each command that is in a transaction block, and
>> rolls back to the savepoint on error.
[snip]
>
> The wording of the option (in combination with the value "on") is
> admittedly confusing. It's really "on_error_continue".
Isn't that the truth. :\
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superior to blacks, and that those with brown skins
are mud people.
However, that "common sense" is obviously wrong.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFQhxsS9HxQb37XmcRAkhIAKDkLRIbOOlNCN4nC1N2DllKfKo5wQCfS/Gk
xHRyVEytS3cQK9y2F8bXeGw=
=wzfH
-----END PGP SIGNATURE-----