Skip site navigation (1) Skip section navigation (2)

Re: Concurrency

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com>
Cc: "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Concurrency
Date: 2010-10-12 20:42:50
Message-ID: 6329.1286916170@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-novice
Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com> writes:
> Where is the problem? The problem lies in the fact that the 2nd 
> transaction should have only seen the changes committed before it has 
> begun, ie, x=1.

You might want to go reread this:
http://www.postgresql.org/docs/9.0/static/transaction-iso.html#XACT-READ-COMMITTED
If you don't like that behavior, you might want SERIALIZABLE mode
instead.

			regards, tom lane

In response to

  • Concurrency at 2010-10-12 20:21:02 from Mladen Gogala

Responses

pgsql-novice by date

Next:From: Mladen GogalaDate: 2010-10-12 20:59:37
Subject: Re: Concurrency
Previous:From: Mladen GogalaDate: 2010-10-12 20:21:02
Subject: Concurrency

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group