Re: PostgreSQL Limits: maximum number of columns in SELECT result - Mailing list pgsql-hackers

From David Rowley
Subject Re: PostgreSQL Limits: maximum number of columns in SELECT result
Date
Msg-id CAApHDvoNwwHKJbNkfuHsWeL5dLeJvaPmTwY26xwrtriyzSd-kQ@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 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



pgsql-hackers by date:

Previous
From: Gavin Flower
Date:
Subject: Re: PostgreSQL Limits: maximum number of columns in SELECT result
Next
From: Tom Lane
Date:
Subject: Re: PostgreSQL Limits: maximum number of columns in SELECT result