Re: PostgreSQL Limits: maximum number of columns in SELECT result

Dave Cramer <davecramer@postgres.rocks>

From: Dave Cramer <davecramer@postgres.rocks>
To: Amul Sul <sulamul@gmail.com>
Cc: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-05-31T14:02:48Z
Lists: pgsql-hackers
On Tue, 31 May 2022 at 09:56, Amul Sul <sulamul@gmail.com> wrote:

> On Tue, May 31, 2022 at 12:46 PM Vladimir Sitnikov
> <sitnikov.vladimir@gmail.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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Doc: mention limitation of the number of resultset columns