Quick Links

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

From:	"David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To:	David Rowley <dgrowleyml(at)gmail(dot)com>
Cc:	德哥 <digoal(at)126(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject:	Re: BUG #17127: drop column cann't delete from pg_attribute, so it will up to 1600 limits soon
Date:	2021-07-29 04:26:55
Message-ID:	CAKFQuwYU3JSnisgVoaEVyPmXgCwEJ5ayZSgWA+-59w2txE+71Q@mail.gmail.com
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-bugs

On Wed, Jul 28, 2021 at 9:15 PM David Rowley <dgrowleyml(at)gmail(dot)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.

	From	Date	Subject
Next Message	Tom Lane	2021-07-29 04:32:52	Re: BUG #17127: drop column cann't delete from pg_attribute, so it will up to 1600 limits soon
Previous Message	David Rowley	2021-07-29 04:14:49	Re: BUG #17127: drop column cann't delete from pg_attribute, so it will up to 1600 limits soon