Re: attndims, typndims still not enforced, but make the value within a sane threshold - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: attndims, typndims still not enforced, but make the value within a sane threshold
Date
Msg-id Z1Hc4reI2W5M8ldb@momjian.us
Whole thread Raw
In response to Re: attndims, typndims still not enforced, but make the value within a sane threshold  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: attndims, typndims still not enforced, but make the value within a sane threshold
List pgsql-hackers
On Thu, Dec  5, 2024 at 12:00:30PM -0500, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.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.

I guess I just don't want to get into a situation where we have so many
useless backward-compatible system columns it is distracting.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.





pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: attndims, typndims still not enforced, but make the value within a sane threshold
Next
From: Alvaro Herrera
Date:
Subject: Re: [Bug] Heap Use After Free in Window Aggregate Execution