| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Steve Baldwin <steve(dot)baldwin(at)gmail(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Lock timeout in commit |
| Date: | 2025-07-10 15:28:46 |
| Message-ID: | 1529239.1752161326@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Steve Baldwin <steve(dot)baldwin(at)gmail(dot)com> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mircea Cadariu | 2025-07-10 16:20:02 | Re: analyze-in-stages post upgrade questions |
| Previous Message | DINESH NAIR | 2025-07-10 14:22:48 | Re: PostgresSQL Setup error |