From: "Michel SALAIS" <msalais@msym.fr>
To: "'Simon Riggs'" <simon@2ndquadrant.com>
Cc: "'Yambu'" <hyambu@gmail.com>,
	"'Pgsql-admin'" <pgsql-admin@lists.postgresql.org>
References: 
 <CALhHtcCVbvXq+6Ekv7RE91XPb=vLYvY2patRFv91SLAQzN4oHw@mail.gmail.com>
 <01b901d6be5d$8952cfb0$9bf86f10$@msym.fr>
 <CANP8+j+OWE7+HtegL=N+gxPLdifRDYoveUuX2qYyDYUgD9hdPQ@mail.gmail.com>
In-Reply-To: 
 <CANP8+j+OWE7+HtegL=N+gxPLdifRDYoveUuX2qYyDYUgD9hdPQ@mail.gmail.com>
Subject: RE: select locks table for updates
Date: Thu, 19 Nov 2020 23:31:59 +0100
Message-ID: <003601d6bec3$cc0db980$64292c80$@msym.fr>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQKYEE4dpos6rE8Iap91JsG09J0k0gJjyiUVAY+wKxCoLclb8A==
Content-Language: fr
Precedence: bulk

I think the original question wasn't about what can be done. Any way =
that is how I considered it. A simple question, a simple reply taking =
into account default behavior only. The point was just to say that =
things don't go the same everywhere...

Michel SALAIS

-----Message d'origine-----
De : Simon Riggs <simon@2ndquadrant.com>=20
Envoy=C3=A9 : jeudi 19 novembre 2020 22:14
=C3=80 : Michel SALAIS <msalais@msym.fr>
Cc : Yambu <hyambu@gmail.com>; Pgsql-admin =
<pgsql-admin@lists.postgresql.org>
Objet : Re: select locks table for updates

On Thu, 19 Nov 2020 at 10:20, Michel SALAIS <msalais@msym.fr> wrote:
>
> No! Not in PostgreSQL.

In normal SELECTs, that is correct.

If you use SELECT ... FOR UPDATE then rows will be locked.

--=20
Simon Riggs                http://www.EnterpriseDB.com/