Re: attndims, typndims still not enforced, but make the value within a sane threshold

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Kirill Reshke <reshkekirill(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: attndims, typndims still not enforced, but make the value within a sane threshold
Date: 2024-12-05 17:00:30
Message-ID: 2542644.1733418030@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Thu, Dec 5, 2024 at 11:33:22AM -0500, Tom Lane wrote:
>> I don't think we can do this as presented. Maybe we could do
>> something like constrain the stored value to be only 0 or 1,
>> but how much does that improve matters?

> Well, then the question becomes will we retain useless system columns
> forever?

If the choice is "not break PHP" versus "get rid of a vestigial column",
I know which one is the saner choice. There might be things that are
worth breaking PHP for, but this isn't one.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2024-12-05 17:03:30 Re: attndims, typndims still not enforced, but make the value within a sane threshold
Previous Message Karina Litskevich 2024-12-05 16:53:59 Potential null pointer dereference in postgres.c