Re: Transaction isolation level Repeatable Read Read Only vs Serializable Read Only

On Thu, 2020-11-26 at 23:45 +0100, Jan Behrens wrote: > I understand that in a read+write scenario, two concurrent transactions may > still lead to > a result that could not have occurred if those two transactions were > executed one after the other. > However, in a read-only case, I do not see

Re: Transaction isolation level Repeatable Read Read Only vs Serializable Read Only

On Thu, 26 Nov 2020 19:13:53 -0500 Mohamed Wael Khobalatte wrote: > > > > Thus, what does SERIALIZABLE READ ONLY achieve that REPEATABLE READ READ > > ONLY does not? And what is SERIALIZABLE READ ONLY DEFERRABLE for? > > > > There is a nice walkthrough of the "control" and "batches/details" scen

Re: Transaction isolation level Repeatable Read Read Only vs Serializable Read Only

> > Thus, what does SERIALIZABLE READ ONLY achieve that REPEATABLE READ READ > ONLY does not? And what is SERIALIZABLE READ ONLY DEFERRABLE for? > There is a nice walkthrough of the "control" and "batches/details" scenario mentioned in the docs, you can find it in the wiki,

Transaction isolation level Repeatable Read Read Only vs Serializable Read Only

Dear all, I have some questions regarding the transaction isolation level REPEATABLE READ and it's documentation at [1] https://www.postgresql.org/docs/13/transaction-iso.html and [2] https://www.postgresql.org/docs/13/sql-set-transaction.html As far as I understood, a read-only transaction wit