public inbox for [email protected]
help / color / mirror / Atom feedFrom: Steve Baldwin <[email protected]>
To: Tom Lane <[email protected]>
Cc: pgsql-generallists.postgresql.org <[email protected]>
Subject: Re: Lock timeout in commit
Date: Fri, 11 Jul 2025 06:32:45 +1000
Message-ID: <CAKE1AiYMY2wk5BhACRvFhyNoKhJ9thhfaQ07DnFO-Ogg0oeENw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAKE1AiY17RgcKCFba1N6Sz6SjHqSqvq+cfKWBfyKFEjT-L+qkg@mail.gmail.com>
<[email protected]>
On Fri, 11 Jul 2025 at 01:28, Tom Lane <[email protected]> wrote:
>
> 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.
>
> Thanks Tom !!
The application is an API server so we intentionally set the lock timeout
to a very short interval (5 ms). Having locking context would be great.
Other than deferred FK constraints, what other locking actions are deferred
to commit time?
Cheers,
Steve
view thread (3+ messages)
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: <CAKE1AiYMY2wk5BhACRvFhyNoKhJ9thhfaQ07DnFO-Ogg0oeENw@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