Re: BUG #17127: drop column cann't delete from pg_attribute, so it will up to 1600 limits soon - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #17127: drop column cann't delete from pg_attribute, so it will up to 1600 limits soon
Date
Msg-id CAKFQuwYU3JSnisgVoaEVyPmXgCwEJ5ayZSgWA+-59w2txE+71Q@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17127: drop column cann't delete from pg_attribute, so it will up to 1600 limits soon  (David Rowley <dgrowleyml@gmail.com>)
List pgsql-bugs
On Wed, Jul 28, 2021 at 9:15 PM David Rowley <dgrowleyml@gmail.com> wrote:

I'm not sure if I agree that it's "explicitly documented".

You apparently didn't "see the last paragraph.".  I quote the relevant (first) sentence below:

"Columns that have been dropped from the table also contribute to the maximum column limit."

David J.

pgsql-bugs by date:

Previous
From: David Rowley
Date:
Subject: Re: BUG #17127: drop column cann't delete from pg_attribute, so it will up to 1600 limits soon
Next
From: Tom Lane
Date:
Subject: Re: BUG #17127: drop column cann't delete from pg_attribute, so it will up to 1600 limits soon