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: 德哥 <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:07:35
Message-ID: CAKFQuwYVbVSTYR2pAc4tDsBMzh6gjHkNehia0NyFHorGSBh3FQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jul 28, 2021 at 8:04 PM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 17127
> Logged by: Zhou Digoal
> Email address: digoal(at)126(dot)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:

https://www.postgresql.org/docs/13/limits.html

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

David J.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next 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
Previous Message David Rowley 2021-07-29 03:35:04 Re: BUG #17127: drop column cann't delete from pg_attribute, so it will up to 1600 limits soon