Re: Waiting for Commit

From: "Pablo Montilla" <melkor(at)adinet(dot)com(dot)uy>
To: "Pablo Montilla" <melkor(at)adinet(dot)com(dot)uy>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Waiting for Commit
Date: 2004-03-28 02:14:36
Message-ID: 004d01c4146a$9a084a60$601d28c8@athena
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well, don't you love when in fact it is YOUR code that's at fault?
Let me assure you that I really tried to blame myself first (did it
for arround 12hours to no avail), but when all else fails...;o)

What I was REALLY doing:

Session1>SET TRANSACTION ISOLATION LEVEL READ COMMITTED; BEGIN;
Session1>INSERT INTO test VALUES(1, 'test');
Session1>COMMIT;
Session1>ROLLBACK;
Session2>SELECT * FROM test;

It seems odd to me that the ROLLBACK was affecting the execution
(couldn't replicate the behavior in psql, maybe its a speed
thing...).

Anyway, many thanks for your time,
Pablo

PS: For anyone who cares, the ROLLBACK was generated by disposing the
NpgsqlTransaction, no matter it was committed. I will post it as a
bug, as Disposing should not be generating that nasty ROLLBACK...;o)
- --
Artificial intelligence is no match for natural stupidity.

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQGY1Cr6KEogX0AkqEQJi6QCfd9pKE4ShhHyE8bWPcpR0qSuNf1EAoP0h
EF3Ya0/yGI5Bpj9T110coMu+
=+AVZ
-----END PGP SIGNATURE-----

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David Garamond 2004-03-28 05:18:28 Re: Index usage for BYTEA column in OR/IN clause
Previous Message Pablo Montilla 2004-03-28 00:41:17 Re: Waiting for Commit