public inbox for [email protected]
help / color / mirror / Atom feedFrom: Greg Sabino Mullane <[email protected]>
To: Nico Heller <[email protected]>
Cc: [email protected]
Subject: Re: Guarantee order of batched pg_advisory_xact_lock
Date: Tue, 17 Feb 2026 09:55:30 -0500
Message-ID: <CAKAnmmJoX=KJyH2g8tWtbSoqJp7nnyeBChaLgF6bbGv1zGLzwg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
On Mon, Feb 16, 2026 at 12:45 PM Nico Heller <[email protected]> wrote:
> Does anyone have any idea what the root cause of my issue is? I appreciate
> any insight.
> As I said, hash collisions can be rules out, sadly.
>
Well, you could set log_statement to 'all' for a bit to see *exactly* what
each of the deadlocking processes are doing. Alternatively, perhaps you can
write a hashextendedkey() function that outputs arguments and results to a
log and/or a table.
keysToLock is a text[] parameter which is pre-sorted in our application
Would not hurt to triple-check this part as well. Could show us the app
code? Maybe put in some sort of global assert in the app to verify that
things are indeed sorted as you think they are.
Cheers,
Greg
--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support
view thread (6+ messages) latest in thread
reply
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: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Guarantee order of batched pg_advisory_xact_lock
In-Reply-To: <CAKAnmmJoX=KJyH2g8tWtbSoqJp7nnyeBChaLgF6bbGv1zGLzwg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox