Downloads
Home   >   mailing lists

Re: Lock timeout in commit - Mailing list pgsql-general

From Steve Baldwin
Subject Re: Lock timeout in commit
Date
Msg-id CAKE1AiYMY2wk5BhACRvFhyNoKhJ9thhfaQ07DnFO-Ogg0oeENw@mail.gmail.com
Whole thread Raw
In response to Re: Lock timeout in commit  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Tree view
On Fri, 11 Jul 2025 at 01:28, Tom Lane <tgl@sss.pgh.pa.us> 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

pgsql-general by date:

Previous
From: Greg Hennessy
Date:
Subject: optimizing number of workers
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin