Re: [BackendXidGetPid] only access allProcs when xid matches - Mailing list pgsql-hackers

From Junwang Zhao
Subject Re: [BackendXidGetPid] only access allProcs when xid matches
Date
Msg-id CAEG8a3JUYLmD5N-3JTtHq1EtsKGhwFVg7JZU6dgS3xwzJFOgTQ@mail.gmail.com
Whole thread Raw
In response to Re: [BackendXidGetPid] only access allProcs when xid matches  (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>)
Responses Re: [BackendXidGetPid] only access allProcs when xid matches
List pgsql-hackers
On Thu, Aug 10, 2023 at 4:11 PM Ashutosh Bapat
<ashutosh.bapat.oss@gmail.com> wrote:
>
> Please add this to commitfest so that it's not forgotten.
>

Added [1], thanks

[1]: https://commitfest.postgresql.org/44/4495/

> On Wed, Aug 9, 2023 at 8:37 PM Junwang Zhao <zhjwpku@gmail.com> wrote:
> >
> > On Wed, Aug 9, 2023 at 10:46 PM Ashutosh Bapat
> > <ashutosh.bapat.oss@gmail.com> wrote:
> > >
> > > On Wed, Aug 9, 2023 at 9:30 AM Junwang Zhao <zhjwpku@gmail.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



--
Regards
Junwang Zhao



pgsql-hackers by date:

Previous
From: Laetitia Avrot
Date:
Subject: Re: Adding a pg_servername() function
Next
From: Ashutosh Bapat
Date:
Subject: Re: Report planning memory in EXPLAIN ANALYZE