Horton
Menu

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

David Rowley <dgrowleyml@gmail.com>

View thread
From: David Rowley <dgrowleyml@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: davecramer@postgres.rocks, 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:51:24Z
Lists: pgsql-hackers 
On Wed, 1 Jun 2022 at 12:42, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> David Rowley <dgrowleyml@gmail.com> writes:
> > I've adjusted the patch to use the wording proposed by Alvaro. See attached.
>
> Should we also change the adjacent item to "columns in a table",
> for consistency of wording?  Not sure though, because s/per/in a/
> throughout the list doesn't seem like it'd be an improvement.

I might agree if there weren't so many other "per"s in the list.

Maybe "columns per result set" would have been a better title for consistency.

David

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