Re: Regarding experiencing - Mailing list pgsql-docs

From Blessy Thomas
Subject Re: Regarding experiencing
Date
Msg-id CAJyyjtBOjgUHmavCbzodgtXGSuPXmw7Ee40cDUTbAutBBWix9Q@mail.gmail.com
Whole thread Raw
In response to Re: Regarding experiencing  (Álvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-docs
Thank you for the clarification. Now this explains the scenario.
Regards
Blessy Thomas

On Tue, 11 Feb 2025 at 15:56, Álvaro Herrera <alvherre@alvh.no-ip.org> wrote:
On 2025-Feb-11, Blessy Thomas wrote:

> These are the  commands I have run in the terminal
> psql (17.0)
> Type "help" for help.
>
> postgres=# SELECT pg_advisory_lock_shared(1001); //initialising the shared
> lock
>  pg_advisory_lock_shared
> -------------------------
>
> (1 row)
>
> postgres=# SELECT pg_advisory_lock(1001); //exclusive lock
>  pg_advisory_lock
> ------------------
>
> (1 row)

Ah yes, there's no conflict in this case because the holder of both
locks is the same session.  You'd have to request the exclusive lock in
another psql session and you should see it block.

--
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/

pgsql-docs by date:

Previous
From: Álvaro Herrera
Date:
Subject: Re: Regarding experiencing
Next
From: PG Doc comments form
Date:
Subject: Second paragraph a little bit misleading