Re: Add new wait event to XactLockTableWait - Mailing list pgsql-hackers

From Xuneng Zhou
Subject Re: Add new wait event to XactLockTableWait
Date
Msg-id CABPTF7VfqEnb6PQGQ0f+b6e7-3EBUyS0reyUK2=ptgCDX2GPwg@mail.gmail.com
Whole thread Raw
In response to Add new wait event to XactLockTableWait  (Xuneng Zhou <xunengzhou@gmail.com>)
List pgsql-hackers
Just CC.

On Mon, Jun 9, 2025 at 10:57 AM Xuneng Zhou <xunengzhou@gmail.com> wrote:
>
> Hi Michael,
>
> Thanks for reviewing.
>
> On Mon, Jun 9, 2025 at 6:41 AM Michael Paquier <michael@paquier.xyz> wrote:
>
> > +     pgstat_report_wait_start(WAIT_EVENT_XACT_DONE);
> > [...]
> > +     pgstat_report_wait_start(WAIT_EVENT_XACT_DONE);
> >
> > Wouldn't it be better to use two wait events named differently to be
> > able to make the difference between the two code paths?
> > --
>
> Both `XactLockTableWait()` and its conditional sibling ultimately
> block on the same thing: “other transaction must commit or abort
> before I can proceed.”  I think that using one identifier might keep
> the catalog simple.
>
> Best regards,
> Xuneng



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Add new wait event to XactLockTableWait
Next
From: Xuneng Zhou
Date:
Subject: Re: Add new wait event to XactLockTableWait