Re: TupleDescAttr bounds checks

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: TupleDescAttr bounds checks
Date: 2026-03-20 17:02:35
Message-ID: CA+TgmoYpi48MV1RoqkLpwSg5b-ySYJ6Vx5yXjOS3hS6oJWwtzw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 20, 2026 at 12:46 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.)

Ah, OK. Yeah, I wasn't completely sure at the time whether there was
some kind of TupleDesc out there that would allow zero or negative
indexes safely. It seems like there is not.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jianghua Yang 2026-03-20 17:02:44 basebackup: add missing deflateEnd() in gzip compression sink
Previous Message Gyan Sreejith 2026-03-20 17:00:14 Re: [Proposal] Adding Log File Capability to pg_createsubscriber