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: Tom Lane <tgl@sss.pgh.pa.us>
Cc: 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-05-31T19:07:56Z
Lists: pgsql-hackers

Attachments

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

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