> 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

Wed, 28 Mar 2001 10:10:02 -0800
"Mikheev, Vadim" <vmikheev@SECTORBASE.COM>
RE: Re: [SQL] possible row locking bug in 7.0.3 & 7.1 
"Mikheev, Vadim" <vmikheev@SECTORBASE.COM> writes:
> Hm, you're right:
> http://www.postgresql.org/devel-corner/docs/postgres/xact-read-committed.html

> "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.

Will fix this shortly...

			regards, tom lane

Wed, 28 Mar 2001 15:24:29 -0500
Tom Lane <tgl@sss.pgh.pa.us>
Re: Re: [SQL] possible row locking bug in 7.0.3 & 7.1 