> On Mar 30, 2025, at 21:44, 이현진 <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.
There are two different questions here.
1. Reads are not blocked in PostgreSQL by writers, even if another transaction
has updated the row but not yet committed.
2. There is no equivalent of a dirty read in PostgreSQL. You can only read
committed data (short of bypassing the database and reading the disk directly).
