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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Dave Cramer <davecramer(at)postgres(dot)rocks>, 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-05-31 18:51:09
Message-ID: 271112.1654023069@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> I think it's reasonable to have two adjacent rows in the table for these
> two closely related things, but rather than "columns per tuple" I would
> label the second one "columns in a result set". This is easy enough to
> understand and to differentiate from the other limit.

OK, with that wording it's probably clear enough.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Cramer 2022-05-31 19:07:56 Re: PostgreSQL Limits: maximum number of columns in SELECT result
Previous Message Tomas Vondra 2022-05-31 18:44:26 Re: Improving connection scalability (src/backend/storage/ipc/procarray.c)