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

On Tue, 31 May 2022 at 20:33, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:

> On Wed, 1 Jun 2022 at 07:08, Dave Cramer <davecramer(at)postgres(dot)rocks>
> wrote:
> >
> > On Tue, 31 May 2022 at 14:51, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >>
> >> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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.
>
> > Reworded patch attached
>
> I see the patch does not have the same text as what was proposed and
> seconded above. My personal preferences would be "result set
> columns", but "columns in a result set" seems fine too.
>
> I've adjusted the patch to use the wording proposed by Alvaro. See
> attached.
>
> I will push this shortly.
>
> David
>

Thanks David, Apparently I am truly unable to multi-task.

Dave