From: Tom Lane <tgl@sss.pgh.pa.us>
To: msalais@msym.fr
cc: "'Rajesh Kumar'" <rajeshkumar.dba09@gmail.com>,
        pgsql-admin@lists.postgresql.org
Subject: Re: Commit with wait event on advisory lock!
In-reply-to: <011401db6d19$1d98ba40$58ca2ec0$@msym.fr>
References: <00c201db6c13$7a1fbb80$6e5f3280$@msym.fr>
 <CAJk5AtY-TWUYU7TR3KfbOyzvfDytTFTJfVyB1cKWpwKxNSV3Ww@mail.gmail.com>
 <00e801db6c63$acd0f8a0$0672e9e0$@msym.fr> <3505513.1737506928@sss.pgh.pa.us>
 <010f01db6cf1$c07f7be0$417e73a0$@msym.fr> <3938129.1737566668@sss.pgh.pa.us>
 <011401db6d19$1d98ba40$58ca2ec0$@msym.fr>
Comments: In-reply-to <msalais@msym.fr>
	message dated "Wed, 22 Jan 2025 23:00:56 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4167141.1737584262.1@sss.pgh.pa.us>
Date: Wed, 22 Jan 2025 17:17:42 -0500
Message-ID: <4167142.1737584262@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/4167142.1737584262%40sss.pgh.pa.us>
Precedence: bulk

<msalais@msym.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