Re: Use correct type for catalog_xmin - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Use correct type for catalog_xmin
Date
Msg-id CAA4eK1JENdPiJmW2xS00i954oUgfX-cYZ-2WhPU+1nkRCTG+wg@mail.gmail.com
Whole thread
In response to Re: Use correct type for catalog_xmin  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Mon, Jun 8, 2026 at 11:05 AM Fujii Masao <masao.fujii@gmail.com> wrote:
>
> On Fri, Jun 5, 2026 at 8:52 PM Ashutosh Bapat
> <ashutosh.bapat.oss@gmail.com> wrote:
> >
> > On Fri, Jun 5, 2026 at 3:33 PM Imran Zaheer <imran.zhir@gmail.com> wrote:
> > >
> > > Hi
> > >
> > > In commit 85c17f6, the variable old_catalog_xmin is using the type
> > > XLogRecPtr, even though data.catalog_xmin is a TransactionId.
> > >
> > > Attached patch fixes this by using TransactionId instead
> >
> > Yes. Looks like a copy-pasto in 85c17f612af7b9c47a9828805686f0dd2433cdf1.
> >
> > Patch LGTM.
>
> LGTM.
>
> This does not seem to cause any functional issue even without the fix,
> since the variable is only used for an equality check. However, the type
> is clearly incorrect, so I think it's better to backpatch it through v17.
>

+1.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: bugfix - fix broken output in expanded aligned format, when data are too short
Next
From: Lukas Fittl
Date:
Subject: Re: RFC: Logging plan of the running query