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

From Gavin Flower
Subject Re: PostgreSQL Limits: maximum number of columns in SELECT result
Date
Msg-id 216a473a-7b36-20a2-735e-567c0acb6e22@archidevsys.co.nz
Whole thread Raw
In response to Re: PostgreSQL Limits: maximum number of columns in SELECT result  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 1/06/22 12:42, Tom Lane 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.
>
>             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




pgsql-hackers by date:

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