From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mike Adelson <mike.adelson314@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #17686: SELECT pg_advisory_lock(...) with low lock_timeout sometimes times out but the lock is acquired
Date: Sat, 12 Nov 2022 13:51:52 -0500
Message-ID: <146790.1668279112@sss.pgh.pa.us> (raw)
In-Reply-To: <F8074C58-D7B7-4A24-9637-429C3B107580@hxcore.ol>
References: <17686-fb1fa3870138e394@postgresql.org>
<63573.1668271677@sss.pgh.pa.us>
<F8074C58-D7B7-4A24-9637-429C3B107580@hxcore.ol>
Mike Adelson <mike.adelson314@gmail.com> writes:
> Glad to have the race condition confirmed. In my view the “real” fix
> here would be to offer an advisory locking function that accepts a
> timeout.
How would that remove the low-level race condition?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, mike.adelson314@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17686: SELECT pg_advisory_lock(...) with low lock_timeout sometimes times out but the lock is acquired
In-Reply-To: <146790.1668279112@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox