| From: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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-05-31 19:07:56 |
| Message-ID: | CADK3HHKVg=pUmqkJid5dMuN8Pj6mXyTEg7v9XSzUyUktTPXZmw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 31 May 2022 at 14:51, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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
>
> Reworded patch attached
| Attachment | Content-Type | Size |
|---|---|---|
| columns_per_tuple.patch | application/octet-stream | 443 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-05-31 19:25:40 | Re: [RFC] building postgres with meson |
| Previous Message | Tom Lane | 2022-05-31 18:51:09 | Re: PostgreSQL Limits: maximum number of columns in SELECT result |