Re: [BackendXidGetPid] only access allProcs when xid matches

From: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
To: Junwang Zhao <zhjwpku(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [BackendXidGetPid] only access allProcs when xid matches
Date: 2023-08-10 08:11:03
Message-ID: CAExHW5voH=E3N3n8fWn03O5BaNZGwnM83XZLc3U4hEsP=jpMhg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Please add this to commitfest so that it's not forgotten.

On Wed, Aug 9, 2023 at 8:37 PM Junwang Zhao <zhjwpku(at)gmail(dot)com> wrote:
>
> On Wed, Aug 9, 2023 at 10:46 PM Ashutosh Bapat
> <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> wrote:
> >
> > On Wed, Aug 9, 2023 at 9:30 AM Junwang Zhao <zhjwpku(at)gmail(dot)com> wrote:
> > >
> > > In function `BackendXidGetPid`, when looping every proc's
> > > TransactionId, there is no need to access its PGPROC since there
> > > is shared memory access: `arrayP->pgprocnos[index]`.
> > >
> > > Though the compiler can optimize this kind of inefficiency, I
> > > believe we should ship with better code.
> > >
> >
> > Looks good to me. However, I would just move the variable declaration
> > with their assignments inside the if () rather than combing the
> > expressions. It more readable that way.
>
> yeah, make sense, also checked elsewhere using the original style,
> attachment file
> keep that style, thanks ;)
>
> >
> > --
> > Best Wishes,
> > Ashutosh Bapat
>
>
>
> --
> Regards
> Junwang Zhao

--
Best Wishes,
Ashutosh Bapat

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Laetitia Avrot 2023-08-10 08:14:46 Re: Adding a pg_servername() function
Previous Message Richard Guo 2023-08-10 08:06:59 Re: Fix last unitialized memory warning