On Fri, 11 Jul 2025 at 01:28, Tom Lane <tgl@xxxxxxxxxxxxx> 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
