Re: TupleDescAttr bounds checks - Mailing list pgsql-hackers

From Tom Lane
Subject Re: TupleDescAttr bounds checks
Date
Msg-id 1631625.1774025167@sss.pgh.pa.us
Whole thread Raw
In response to Re: TupleDescAttr bounds checks  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: TupleDescAttr bounds checks
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, Mar 20, 2026 at 12:22 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I had just come to the same conclusion about why grison is failing.

> Hmm, I had a rougher version of this analysis (and an analysis of some
> the other failures) on an email I sent yesterday on the pg_plan_advice
> thread. Based on this email and another one you sent, I'm guessing you
> either didn't see that email or maybe even didn't get a copy of it for
> some reason.

I did see that, but it read to me that you were just guessing at that
time.  This morning I put Asserts into indexcmds.c that verified that
it was trying to access the tupledesc for attno zero, and that proves
there is a bug there.  It also seems like a plausible explanation for
why only one machine has exhibited the failure.  (Your 0002 is a
better version of said Asserts.)

            regards, tom lane



pgsql-hackers by date:

Previous
From: Japin Li
Date:
Subject: Re: pg_get__*_ddl consolidation
Next
From: Gyan Sreejith
Date:
Subject: Re: [Proposal] Adding Log File Capability to pg_createsubscriber