From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(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:14:49 |
Message-ID: | CAApHDvqnWUmQ5YAPtMwxZM4eH-4NbcLY22zvTQhbXLY4xk3-Yg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, 29 Jul 2021 at 16:08, David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> On Wed, Jul 28, 2021 at 8:04 PM PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:
>> 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.
I'm not sure if I agree that it's "explicitly documented". All that
text mentions is that you can't have more than 1600 columns in a table
at once. What the OP is complaining about are that attnums are not
recycled and that if you continually add and drop columns you can run
out well before you have 1600 columns.
David
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2021-07-29 04:26:55 | Re: BUG #17127: drop column cann't delete from pg_attribute, so it will up to 1600 limits soon |
Previous Message | David G. Johnston | 2021-07-29 04:07:35 | Re: BUG #17127: drop column cann't delete from pg_attribute, so it will up to 1600 limits soon |