Feedback-ID: i76984098:Fastmail
Message-ID: <cee64d43-3763-4e8b-9ca5-559e5c274879@aklaver.com>
Date: Tue, 14 Jan 2025 10:46:19 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Fwd: Lock in postgreSQL
To: Igor Korot <ikorot01@gmail.com>,
 "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
References: <CA+FnnTwP6x6O-DO2RMop5UK5C23OuzEVHFxia3RnV7cXR=84qg@mail.gmail.com>
 <CA+FnnTy9PNY07qa9DJ5yb+gb17MMHpYXVrZLbWcRrPf5Yk7E5w@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CA+FnnTy9PNY07qa9DJ5yb+gb17MMHpYXVrZLbWcRrPf5Yk7E5w@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/cee64d43-3763-4e8b-9ca5-559e5c274879%40aklaver.com>
Precedence: bulk


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@gmail.com>
> Date: Tue, Jan 14, 2025 at 12:50 AM
> Subject: Lock in postgreSQL
> To: pgsql-generallists.postgresql.org
> <pgsql-general@lists.postgresql.org>, PostgreSQL ODBC list
> <pgsql-odbc@postgresql.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.
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com