Re: Fwd: Lock in postgreSQL

[Adrian Klaver <adrian.klaver@xxxxxxxxxxx>]

On 1/14/25 10:42 AM, Igor Korot wrote:
> Hi, ALL,
>
> This concern both libpq and DBC API.
>
> Hopefully I can get answers on both.

Read:

https://www.postgresql.org/docs/current/explicit-locking.html#ADVISORY-LOCKS

> Than yu.
>
>
> ---------- Forwarded message ---------
> From: Igor Korot <ikorot01@xxxxxxxxx>
> Date: Tue, Jan 14, 2025 at 12:50 AM
> Subject: Lock in postgreSQL
> To: pgsql-generallists.postgresql.org
> <pgsql-general@xxxxxxxxxxxxxxxxxxxx>, PostgreSQL ODBC list
> <pgsql-odbc@xxxxxxxxxxxxxx>
>
>
> Hi, ALL,
> https://www.postgresql.org/docs/current/functions-admin.html#FUNCTIONS-ADVISORY-LOCKS
>
> There is an explanation about a promissory
> lock functions().
>
> I have 2 questions about that:
> 1. Is calling one of them a way to get the lock()?
> 2. If I work on ODBC-based connection - I should call SQLExectDirect()
> with the function in question, correct?
>
> Thank you.

--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx