On Sun, 2025-03-30 at 22:10 -0700, David G. Johnston wrote: > On Sunday, March 30, 2025, 이현진 <jemie9...@gmail.com> wrote: > > Since PostgreSQL uses MVCC, I'm wondering what the best practice is for > > non-blocking reads, > > and whether there's an equivalent to dirty reads or READ UNCOMMITTED. > > https://www.postgresql.org/docs/current/transaction-iso.html > > We are unable to implement read uncommitted because of our choice to > implement MVCC.
Perhaps it would be better to say "there is no need to implement a READ UNCOMMITTED isolation level that actually allows for dirty reads". On databases like SQL Server you don't use READ UNCOMMITTED because you desperately want to see dirty, inconsistent data. It is just something you have to accept in order to avoid read locks. Since PostgreSQL doesn't use read locks, there is no need for that. Yours, Laurenz Albe
