RE: Re: [SQL] possible row locking bug in 7.0.3 & 7.1 - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject RE: Re: [SQL] possible row locking bug in 7.0.3 & 7.1
Date
Msg-id 8F4C99C66D04D4118F580090272A7A234D3357@sectorbase1.sectorbase.com
Whole thread Raw
Responses Re: Re: [SQL] possible row locking bug in 7.0.3 & 7.1  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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


pgsql-hackers by date:

Previous
From: "Mikheev, Vadim"
Date:
Subject: RE: Re: [SQL] possible row locking bug in 7.0.3 & 7.1
Next
From: Tom Lane
Date:
Subject: Changing the default value of an inherited column