Re: Add wait event for CommitDelay

From: Sami Imseih <samimseih(at)gmail(dot)com>
To: Rafia Sabih <rafia(dot)pghackers(at)gmail(dot)com>
Cc: Ants Aasma <ants(at)cybertec(dot)at>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add wait event for CommitDelay
Date: 2025-12-05 16:15:19
Message-ID: CAA5RZ0tofDkjnbn3=jKLODEwY7iVKQ_jactCC+HKX88q7G8VhQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

> So, my colleague Ants Aasma found that a wait_event is missing for CommitDelay.
> This just looks like it was missed, please enlighten if it is left out intentionally.

I do not know if it was left out intentionally, there are no comments on that
matter.

I am not sure how widely used this GUC is, but from the quick test that I
did using pgench TPC-B workload with 50 clients, it seems useful
since a DBA can set commit_delay too high and you will easily observe
a single backend constantly in this delay which will impact tps.
It's good to show this clearly as a wait event.

As far as the patch goes, It makes sense to put this under "WaitEventTimeout",
but it should be placed after CHECKPOINT_WRITE_DELAY in
alphabetical order, and the description could be improved a bit.
How about? "Waiting for the commit delay before WAL flush."

--
Sami Imseih
Amazon Web Services (AWS)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-12-05 16:20:50 Re: More const-marking cleanup
Previous Message cca5507 2025-12-05 16:11:39 Re: Support loser tree for k-way merge