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

From: Amul Sul <sulamul(at)gmail(dot)com>
To: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
Cc: 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 13:55:53
Message-ID: CAAJ_b96jycocnr-8cJtZzjLoaS0__WneOKPXQdXXXLE50FQ8CQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Regards,
Amul

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Cramer 2022-05-31 14:02:48 Re: PostgreSQL Limits: maximum number of columns in SELECT result
Previous Message Aleksander Alekseev 2022-05-31 13:49:17 Re: [RFC] building postgres with meson