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 CAKFQuwYVbVSTYR2pAc4tDsBMzh6gjHkNehia0NyFHorGSBh3FQ@mail.gmail.com
Whole thread Raw
In response to BUG #17127: drop column cann't delete from pg_attribute, so it will up to 1600 limits soon  (PG Bug reporting form <noreply@postgresql.org>)
Responses 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 8:04 PM PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      17127
Logged by:          Zhou Digoal
Email address:      digoal@126.com
PostgreSQL version: 14beta2
Operating system:   CentOS 7.7 x64
Description:       

HI, postgresql drop column cann't delete from pg_attribute, so it will up to
1600 limits soon when add and drop column frequenc.


Yes, this fact is explicitly documented.  See the last paragraph here:


So, it is not a bug, and, IMO, it is not a limitation worth removing.

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: David Rowley
Date:
Subject: Re: BUG #17127: drop column cann't delete from pg_attribute, so it will up to 1600 limits soon