| From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
|---|---|
| To: | Xuneng Zhou <xunengzhou(at)gmail(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Kevin K Biju <kevinkbiju(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Add new wait event to XactLockTableWait |
| Date: | 2025-06-09 13:45:57 |
| Message-ID: | CAFiTN-tpedjvn_=VavJj10XDQYneNAx0f2sEmyu6GDeTZJdDuw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 9, 2025 at 6:55 PM Xuneng Zhou <xunengzhou(at)gmail(dot)com> wrote:
>
> Hi Dilip,
>
> Thanks for looking into this!
>
> On Mon, Jun 9, 2025 at 6:56 PM Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
>>
>> > Thanks for updating the patch! It looks good to me.
>> >
>> > I think we can mark it as "Ready for Committer" in the CommitFest.
>> > Unless there are any objections, I'll commit it once v19 development opens.
>>
>> LGTM, except I suggest using WAIT_EVENT_XACT_COMPLETE instead of
>> WAIT_EVENT_XACT_DONE. I think it sounds better.
>
>
> I have renamed it in v3.
Thanks LGTM.
--
Regards,
Dilip Kumar
Google
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2025-06-09 14:25:23 | Re: Cleaning up historical portability baggage |
| Previous Message | Dilip Kumar | 2025-06-09 13:44:41 | Question on error code selection in conflict detection |