From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | msalais(at)msym(dot)fr |
Cc: | "'Rajesh Kumar'" <rajeshkumar(dot)dba09(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Commit with wait event on advisory lock! |
Date: | 2025-01-22 22:17:42 |
Message-ID: | 4167142.1737584262@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
<msalais(at)msym(dot)fr> writes:
> But my concern here is really to understand in which situations, a COMMIT
> statement can wait on a lock especially that I have no triggers, and no
> deferrable constraints...
The core code does nothing with advisory locks. If COMMIT is blocking
on one of those, it must be a consequence of user-defined code that
is running at pre-commit time. You've given us nothing to go on about
what that could be.
> By the way I also have commits which are waiting on ClientRead...
That, on the other hand, is surely impossible. I think maybe you
are misreading the stats display. Typically I'd expect that such a
case indicates that the session is idle (awaiting a new command)
and the COMMIT is the last thing it did before that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mauricio Fernandez | 2025-01-23 01:19:56 | High Availability |
Previous Message | msalais | 2025-01-22 22:00:56 | RE: Commit with wait event on advisory lock! |