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

From: Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: PostgreSQL Limits: maximum number of columns in SELECT result
Date: 2022-06-01 00:50:53
Message-ID: 216a473a-7b36-20a2-735e-567c0acb6e22@archidevsys.co.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1/06/22 12:42, Tom Lane 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.
>
> regards, tom lane
>
>
I like the word 'per' better than the phrase 'in a', at least in this
context.

(Though I'm not too worried either way!)

Cheers,
Gavin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2022-06-01 00:51:24 Re: PostgreSQL Limits: maximum number of columns in SELECT result
Previous Message Tom Lane 2022-06-01 00:42:47 Re: PostgreSQL Limits: maximum number of columns in SELECT result