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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
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:42:47
Message-ID: 376689.1654044167@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gavin Flower 2022-06-01 00:50:53 Re: PostgreSQL Limits: maximum number of columns in SELECT result
Previous Message Dave Cramer 2022-06-01 00:37:35 Re: PostgreSQL Limits: maximum number of columns in SELECT result