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

Gavin Flower <gavinflower@archidevsys.co.nz>

From: Gavin Flower <GavinFlower@archidevsys.co.nz>
To: pgsql-hackers@lists.postgresql.org
Date: 2022-06-01T00:50:53Z
Lists: 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




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