Thank you for the clarification. Now this explains the scenario. Regards Blessy Thomas
On Tue, 11 Feb 2025 at 15:56, Álvaro Herrera <alvhe...@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/ >
