> 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 ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
- Re: [HACKERS] Re: [SQL] possible row locking bug in 7.0.3... Hiroshi Inoue
- RE: [HACKERS] Re: [SQL] possible row locking bug in ... Mikheev, Vadim
- Re: [HACKERS] Re: [SQL] possible row locking bug in ... Mikheev, Vadim
- RE: [HACKERS] Re: [SQL] possible row locking bug in ... Mikheev, Vadim
- Re: [HACKERS] Re: [SQL] possible row locking bug in ... Hiroshi Inoue
- Re: [HACKERS] Re: [SQL] possible row locking bug... Forest Wilkinson
- RE: [HACKERS] Re: [SQL] possible row locking bug in ... Mikheev, Vadim
- Re: [HACKERS] Re: [SQL] possible row locking bug... Hiroshi Inoue
- [HACKERS] Re: [SQL] possible row locking bug in 7.0.... Forest Wilkinson
- RE: [HACKERS] Re: [SQL] possible row locking bug in ... Mikheev, Vadim
- RE: [HACKERS] Re: [SQL] possible row locking bug in ... Mikheev, Vadim