Re: SQL Server's WITH (NOLOCK) equivalent in PostgreSQL?

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: 이현진 <jemie9812(at)gmail(dot)com>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: SQL Server's WITH (NOLOCK) equivalent in PostgreSQL?
Date: 2025-03-31 05:10:54
Message-ID: CAKFQuwYCj-gXZuyrwpP-jycbgH2_HmEsNWvJNDqr0WT2fEp8_A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sunday, March 30, 2025, 이현진 <jemie9812(at)gmail(dot)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. There is no equivalent because the fundamental operating
decisions doesn’t allow for one.

If you don’t pre-suppose the solution of dirty reads and instead supply a
use case and desired constraints maybe an alternative approach for that use
case could be suggested.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2025-03-31 07:58:41 Re: SQL Server's WITH (NOLOCK) equivalent in PostgreSQL?
Previous Message Christophe Pettus 2025-03-31 05:02:18 Re: SQL Server's WITH (NOLOCK) equivalent in PostgreSQL?