Re: pgsql: Document XLOG_INCLUDE_XID a little better - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: pgsql: Document XLOG_INCLUDE_XID a little better
Date
Msg-id CAFiTN-vCznDJuYfCjyQtiVAjHhuHxwASS8eJSe4BPW6jrsbvkQ@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Document XLOG_INCLUDE_XID a little better  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Wed, Oct 20, 2021 at 4:17 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Wed, Oct 20, 2021 at 10:25 AM Dilip Kumar <dilipbalaut@gmail.com> wrote:
> >
> > I have one comment here, basically, you have changed the function name
> > to "IsTopTransactionIdLogged", but it still behaves like
> > IsTopTransactionIdLogPending.  Now with the new name, it should return
> > (CurrentTransactionState->topXidLogged) instead of
> > (!CurrentTransactionState->topXidLogged).
> >
>
> Valid point but I think the change suggested by you won't be
> sufficient. We also need to change all the other checks in that
> function to return true which will make it a bit awkward. So instead,
> we can change the function name to IsTopTransactionIdLogPending().
> Does that make sense?

Yeah, that makes sense.

-- 
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Question about building an exportable snapshop
Next
From: Daniel Gustafsson
Date:
Subject: Re: [PATCH] Fix memory corruption in pg_shdepend.c