From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Strange Behavior with Serializable Transcations |
Date: | 2006-06-28 19:20:49 |
Message-ID: | 20060628192049.GA6760@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Jun 28, 2006 at 02:48:01PM -0400, Brad Nicholson wrote:
> I'm seeing something fairly unintuitive about serializable transactions.
>
> Taking the following test case:
<snip>
> http://www.postgresql.org/docs/8.1/interactive/transaction-iso.html
>
> "When a transaction is on the serializable level, a SELECT query sees
> only data committed before the transaction began; it never sees either
> uncommitted data or changes committed during transaction execution by
> concurrent transactions."
I think the issue here is that transaction begin is not when you type
"begin" but at your first actual query. You can obviously only start a
transaction once you know what serialisation level you want, and you
don't see that till after the begin.
Hope this helps,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
From | Date | Subject | |
---|---|---|---|
Next Message | Karsten Hilbert | 2006-06-28 19:33:18 | Re: empty text fields |
Previous Message | Karen Hill | 2006-06-28 18:59:36 | Is it possible to disable insert/update/delete triggers for one transaction and not another? |