Fwd: Lock in postgreSQL

From: Igor Korot <ikorot01(at)gmail(dot)com>
To: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Fwd: Lock in postgreSQL
Date: 2025-01-14 18:42:41
Message-ID: CA+FnnTy9PNY07qa9DJ5yb+gb17MMHpYXVrZLbWcRrPf5Yk7E5w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi, ALL,

This concern both libpq and DBC API.

Hopefully I can get answers on both.

Than yu.

---------- Forwarded message ---------
From: Igor Korot <ikorot01(at)gmail(dot)com>
Date: Tue, Jan 14, 2025 at 12:50 AM
Subject: Lock in postgreSQL
To: pgsql-generallists.postgresql.org
<pgsql-general(at)lists(dot)postgresql(dot)org>, PostgreSQL ODBC list
<pgsql-odbc(at)postgresql(dot)org>

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.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2025-01-14 18:46:19 Re: Fwd: Lock in postgreSQL
Previous Message Adrian Klaver 2025-01-14 17:56:33 Re: Intermittent errors when fetching cursor rows on PostgreSQL 16