From: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
---|---|
To: | Amul Sul <sulamul(at)gmail(dot)com> |
Cc: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PostgreSQL Limits: maximum number of columns in SELECT result |
Date: | 2022-05-31 14:02:48 |
Message-ID: | CADK3HH+m9B9wzOfYWTtPZnDaxC8X7A7RoSoNRRDs8MrZ3czejQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 31 May 2022 at 09:56, Amul Sul <sulamul(at)gmail(dot)com> wrote:
> On Tue, May 31, 2022 at 12:46 PM Vladimir Sitnikov
> <sitnikov(dot)vladimir(at)gmail(dot)com> wrote:
> >
> > Hi,
> >
> > Today I hit "ERROR: target lists can have at most 1664 entries", and I
> was surprised the limit was not documented.
> >
> > I suggest that the limit of "1664 columns per tuple" (or whatever is the
> right term) should be added
> > to the list at https://www.postgresql.org/docs/current/limits.html e.g.
> after "columns per table".
> >
>
> Rather, I think the "columns per table" limit needs to be updated to 1664.
>
Actually that is correct. Columns per table is MaxHeapAttributeNumber which
is 1600.
MaxTupleAttributeNumber is 1664 and is the limit of user columns in a
tuple.
Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2022-05-31 14:06:35 | Re: Multi-Master Logical Replication |
Previous Message | Amul Sul | 2022-05-31 13:55:53 | Re: PostgreSQL Limits: maximum number of columns in SELECT result |