Horton
Menu

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

Dave Cramer <davecramer@postgres.rocks>

View thread
From: Dave Cramer <davecramer@postgres.rocks>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Amul Sul <sulamul@gmail.com>, Vladimir Sitnikov <sitnikov.vladimir@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-05-31T14:27:16Z
Lists: pgsql-hackers 
On Tue, 31 May 2022 at 10:16, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Amul Sul <sulamul@gmail.com> writes:
> > On Tue, May 31, 2022 at 12:46 PM Vladimir Sitnikov
> > <sitnikov.vladimir@gmail.com> wrote:
> >> 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".
>
> We've generally felt that the existing "columns per table" limit is
> sufficient detail here.
>

ISTM that adding detail is free whereas the readers time to figure out why
and where this number came from is not.

I think it deserves mention.

Regards,
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