| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | davecramer(at)postgres(dot)rocks, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Amul Sul <sulamul(at)gmail(dot)com>, Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PostgreSQL Limits: maximum number of columns in SELECT result |
| Date: | 2022-06-01 00:51:24 |
| Message-ID: | CAApHDvoNwwHKJbNkfuHsWeL5dLeJvaPmTwY26xwrtriyzSd-kQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 1 Jun 2022 at 12:42, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> David Rowley <dgrowleyml(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-06-01 00:55:29 | Re: PostgreSQL Limits: maximum number of columns in SELECT result |
| Previous Message | Gavin Flower | 2022-06-01 00:50:53 | Re: PostgreSQL Limits: maximum number of columns in SELECT result |