Re: PostgreSQL Limits: maximum number of columns in SELECT result
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Amul Sul <sulamul@gmail.com>
Cc: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-05-31T14:16:45Z
Lists: pgsql-hackers
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. > Rather, I think the "columns per table" limit needs to be updated to 1664. That number is not wrong. See MaxTupleAttributeNumber and MaxHeapAttributeNumber: https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/include/access/htup_details.h;h=51a60eda088578188b41f4506f6053c2fb77ef0b;hb=HEAD#l23 regards, tom lane
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Doc: mention limitation of the number of resultset columns
- 9ae467db92ce 12.12 landed
- e6bd7aafc82d 13.8 landed
- f2a0060a9bfb 14.4 landed
- bbb6489042a8 15.0 landed