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

From Tom Lane
Subject Re: PostgreSQL Limits: maximum number of columns in SELECT result
Date
Msg-id 176542.1654008584@sss.pgh.pa.us
Whole thread Raw
In response to Re: PostgreSQL Limits: maximum number of columns in SELECT result  (Dave Cramer <davecramer@postgres.rocks>)
Responses Re: PostgreSQL Limits: maximum number of columns in SELECT result
Re: PostgreSQL Limits: maximum number of columns in SELECT result
Re: PostgreSQL Limits: maximum number of columns in SELECT result
List 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



pgsql-hackers by date:

Previous
From: Ranier Vilela
Date:
Subject: Re: Improving connection scalability (src/backend/storage/ipc/procarray.c)
Next
From: Robert Haas
Date:
Subject: Re: PG15 beta1 sort performance regression due to Generation context change