| From: | Steve Baldwin <steve(dot)baldwin(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Lock timeout in commit |
| Date: | 2025-07-10 12:01:07 |
| Message-ID: | CAKE1AiY17RgcKCFba1N6Sz6SjHqSqvq+cfKWBfyKFEjT-L+qkg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi all,
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? I couldn't see any obvious clue in the log. Is there somewhere
else I can look?
In case it matters, the server is running version 17.4.
Thanks,
Steve
| From | Date | Subject | |
|---|---|---|---|
| Next Message | DINESH NAIR | 2025-07-10 14:22:48 | Re: PostgresSQL Setup error |
| Previous Message | Dominique Devienne | 2025-07-10 11:48:15 | Aggregate versions of hashing functions (md5, sha1, etc...) |