Re: Clarification regarding managing advisory locks in postgresql

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: Sasmit Utkarsh <utkarshsasmit(at)gmail(dot)com>
Cc: Christophe Pettus <xof(at)thebuild(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Clarification regarding managing advisory locks in postgresql
Date: 2024-02-08 20:54:43
Message-ID: CAKAnmmJTL1Q2Bur8_GiiCATsrQMqCAD1W_yL6U63i2-_PYM1MQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Jan 25, 2024 at 5:44 AM Sasmit Utkarsh <utkarshsasmit(at)gmail(dot)com>
wrote:

> Therefore, locks acquired in one process (or transaction) do not directly
> affect locks in another process (or transaction).
>

Um....maybe if you describe the exact problem you are trying to solve with
advisory locks, we can find the best solution. It may not even involve
advisory locks.

Cheers,
Greg

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Justin 2024-02-08 21:25:11 Re: Partitioning options
Previous Message Greg Sabino Mullane 2024-02-08 20:50:34 Re: Partitioning options