Horton
Menu

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

Tom Lane <tgl@sss.pgh.pa.us>

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

Detail is far from "free".  Most readers are going to spend more time
wondering what the difference is between "columns per table" and "columns
per tuple", and which limit applies when, than they are going to save by
having the docs present them with two inconsistent numbers.

			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 →

  1. Doc: mention limitation of the number of resultset columns