public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Steve Baldwin <[email protected]>
Cc: pgsql-generallists.postgresql.org <[email protected]>
Subject: Re: Lock timeout in commit
Date: Thu, 10 Jul 2025 11:28:46 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKE1AiY17RgcKCFba1N6Sz6SjHqSqvq+cfKWBfyKFEjT-L+qkg@mail.gmail.com>
References: <CAKE1AiY17RgcKCFba1N6Sz6SjHqSqvq+cfKWBfyKFEjT-L+qkg@mail.gmail.com>
Steve Baldwin <[email protected]> writes:
> I'm occasionally seeing a lock timeout in a commit statement. For example:
> 2025-07-10 08:56:07.225 UTC,"b2bc_api","b2bcreditonline",23592,"
> 10.124.230.241:60648",686f8022.5c28,55,"COMMIT",2025-07-10 08:56:02
> UTC,3984/10729,676737574,ERROR,55P03,"canceling statement due to lock
> timeout",,,,,,"COMMIT",,,"098c62f7-bb76-4607-88da-120c6edee423","client
> backend",,-2835399305386018931
> Am I right in thinking this is likely due to a deferred foreign key
> constraint?
Plausible guess perhaps, although FKs don't normally need strong
locks.
> I couldn't see any obvious clue in the log. Is there somewhere
> else I can look?
I think all you could do is monitor the pg_locks view and hope to
catch the process in "waiting" state before it fails.
It occurs to me to wonder though if we couldn't provide more
context in the error about what lock is being waited for.
regards, tom lane
view thread (3+ 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], [email protected]
Subject: Re: Lock timeout in commit
In-Reply-To: <[email protected]>
* 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