Re: [HACKERS] Isolation levels READ UNCOMMITTED and REPEATABLE READ

Added to TODO: * Allow more ISOLATION LEVELS to be accepted, but issue a warning for them --- Tom Lane wrote: Peter Eisentraut [EMAIL PROTECTED] writes: I think we could allow users to set the

Re: [HACKERS] Isolation levels READ UNCOMMITTED and REPEATABLE READ

Peter Eisentraut [EMAIL PROTECTED] writes: I think we could allow users to set the transaction isolation level to READ UNCOMMITTED or REPEATABLE READ and internally behave like READ COMMITTED or SERIALIZABLE, respectively. The SQL standard seems to allow this: My reading is that the spec

[HACKERS] Isolation levels READ UNCOMMITTED and REPEATABLE READ

I think we could allow users to set the transaction isolation level to READ UNCOMMITTED or REPEATABLE READ and internally behave like READ COMMITTED or SERIALIZABLE, respectively. The SQL standard seems to allow this: [speaking about SET TRANSACTION] 5) The isolation level of TXN is

Re: [HACKERS] Isolation levels READ UNCOMMITTED and REPEATABLE READ

On Thu, 9 Oct 2003, Peter Eisentraut wrote: I think we could allow users to set the transaction isolation level to READ UNCOMMITTED or REPEATABLE READ and internally behave like READ COMMITTED or SERIALIZABLE, respectively. The SQL standard seems to allow this: Why not. I would like a