MIME-Version: 1.0
From: =?UTF-8?B?7J207ZiE7KeE?= <jemie9812@gmail.com>
Date: Mon, 31 Mar 2025 13:44:10 +0900
Message-ID: <CAH0WOV4JhR3OgjNg69h-ZY9o1ooWq=32aa4GrSL5a3y41nApHQ@mail.gmail.com>
Subject: SQL Server's WITH (NOLOCK) equivalent in PostgreSQL?
To: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000dc684106319c12fb"
Archived-At: <https://www.postgresql.org/message-id/CAH0WOV4JhR3OgjNg69h-ZY9o1ooWq%3D32aa4GrSL5a3y41nApHQ%40mail.gmail.com>
Precedence: bulk

--000000000000dc684106319c12fb
Content-Type: text/plain; charset="UTF-8"

Hi all,

I'm trying to understand how to replicate SQL Server's WITH (NOLOCK)
behavior in PostgreSQL.
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.

Would appreciate any insights or recommended approaches.

--000000000000dc684106319c12fb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<br><br>I&#39;m trying to understand how to replica=
te SQL Server&#39;s WITH (NOLOCK) behavior in PostgreSQL.<br>Since PostgreS=
QL uses MVCC, I&#39;m wondering what the best practice is for non-blocking =
reads, <br>and whether there&#39;s an equivalent to dirty reads or READ UNC=
OMMITTED.<br><br>Would appreciate any insights or recommended approaches.<b=
r></div>

--000000000000dc684106319c12fb--