Horton
Menu

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

Dave Cramer <davecramer@postgres.rocks>

View thread
From: Dave Cramer <davecramer@postgres.rocks>
To: David Rowley <dgrowleyml@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Amul Sul <sulamul@gmail.com>, Vladimir Sitnikov <sitnikov.vladimir@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-06-01T00:37:35Z
Lists: pgsql-hackers 
On Tue, 31 May 2022 at 20:33, David Rowley <dgrowleyml@gmail.com> wrote:

> On Wed, 1 Jun 2022 at 07:08, Dave Cramer <davecramer@postgres.rocks>
> wrote:
> >
> > 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.
>
> > 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

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