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 CADK3HHKVg=pUmqkJid5dMuN8Pj6mXyTEg7v9XSzUyUktTPXZmw@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


On Tue, 31 May 2022 at 14:51, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> I think it's reasonable to have two adjacent rows in the table for these
> two closely related things, but rather than "columns per tuple" I would
> label the second one "columns in a result set".  This is easy enough to
> understand and to differentiate from the other limit.

OK, with that wording it's probably clear enough.

                        regards, tom lane

Reworded patch attached
 
Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PostgreSQL Limits: maximum number of columns in SELECT result
Next
From: Andres Freund
Date:
Subject: Re: [RFC] building postgres with meson