Postgres Pro
Downloads
Home   >   mailing lists

Re: PostgreSQL Limits: maximum number of columns in SELECT result - Mailing list pgsql-hackers

From Dave Cramer
Subject Re: PostgreSQL Limits: maximum number of columns in SELECT result
Date
Msg-id CADK3HH+SBsb1wZB2kU1KAtiPb8kE-TLabvwtBy1UiZ7gzO==hg@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL Limits: maximum number of columns in SELECT result  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PostgreSQL Limits: maximum number of columns in SELECT result
List pgsql-hackers
Tree view


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.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PostgreSQL Limits: maximum number of columns in SELECT result
Next
From: Zhihong Yu
Date:
Subject: Re: adding status for COPY progress report