Re: BUG #6052: ADD COLUMN - ERROR: tables can have at most 1600 columns

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Juris Kaminskis <juris(dot)kaminskis(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6052: ADD COLUMN - ERROR: tables can have at most 1600 columns
Date: 2023-09-18 15:22:02
Message-ID: CAKFQuwanuw6kj8PpP9xXeETsJaXoheYOWytBh9S807gytFGQTA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Sep 18, 2023 at 8:03 AM Juris Kaminskis <juris(dot)kaminskis(at)gmail(dot)com>
wrote:

> I would like to refresh this problem again.
>

This isn't a bug so this isn't the place to discuss it. If all you want to
do is try and get a bunch of +1s for the idea, post your use case to
-general and see who else agrees with you. But I don't see it being very
likely that this particular limit goes away. Especially if the last
reported request is from the 8.4 days of PostgreSQL and you aren't offering
a patch.

A staging table that isn't built from scratch each time isn't a use case
I'd be too interested in spending significant effort to handle. And a test
harness that doesn't have an initializer to build out clean first-run
tables on demand falls into basically the same category.

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Philip Muturura 2023-09-18 16:36:06 Installing PostgreSQL 16 on FreeBSD 13.0
Previous Message Juris Kaminskis 2023-09-18 14:16:47 Re: BUG #6052: ADD COLUMN - ERROR: tables can have at most 1600 columns