Hello Tom
I do have delays sometimes because of synchronous_commit (We use actually
the default value and synchronous_standby_names is not empty). I have
sometimes commit execution time more than 10 sec but the problem is more
general than commit/synchronization.
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...
What could it be? This can point something to look about...
By the way I also have commits which are waiting on ClientRead...
--
Michel SALAIS
-----Message d'origine-----
De : Tom Lane <tgl@sss.pgh.pa.us>
Envoyé : mercredi 22 janvier 2025 18:24
À : msalais@msym.fr
Cc : 'Rajesh Kumar' <rajeshkumar.dba09@gmail.com>;
pgsql-admin@lists.postgresql.org
Objet : Re: Commit with wait event on advisory lock!
<msalais@msym.fr> writes:
> - Replication is used (2 standby, one sync and the other potential)
> but no application connection to replica.
Maybe you have synchronous_commit set to enforce waiting for the standby to
receive/apply the transaction? If so I'd look for possible delays there.
regards, tom lane
