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

RE: Re: [SQL] possible row locking bug in 7.0.3 & 7.1

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Philip Warner'" <pjw(at)rhyme(dot)com(dot)au>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: RE: Re: [SQL] possible row locking bug in 7.0.3 & 7.1
Date: 2001-03-28 18:10:02
Message-ID: 8F4C99C66D04D4118F580090272A7A234D3357@sectorbase1.sectorbase.com (view raw or flat)
Thread:
Lists: pgsql-hackers
> Looking at the docs, I see that 'SERIALIZABLE' has the same visibility
> rules as 'READ COMMITTED', which is very confusing. I expect 

Hm, you're right:
http://www.postgresql.org/devel-corner/docs/postgres/xact-read-committed.htm
l

"Read Committed is the default isolation level in Postgres. When
a transaction runs on this isolation level, a SELECT query sees only
data committed before the transaction began..."
     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Must be "committed before the *query* began" as it was in 6.5 docs.
Any way to fix it before release?

Vadim

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2001-03-28 18:30:30
Subject: Changing the default value of an inherited column
Previous:From: Mikheev, VadimDate: 2001-03-28 17:58:43
Subject: RE: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1

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