| From: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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 14:27:16 |
| Message-ID: | CADK3HH+SBsb1wZB2kU1KAtiPb8kE-TLabvwtBy1UiZ7gzO==hg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 31 May 2022 at 10:16, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Amul Sul <sulamul(at)gmail(dot)com> writes:
> > On Tue, May 31, 2022 at 12:46 PM Vladimir Sitnikov
> > <sitnikov(dot)vladimir(at)gmail(dot)com> wrote:
> >> I suggest that the limit of "1664 columns per tuple" (or whatever is
> the right term) should be added
> >> to the list at https://www.postgresql.org/docs/current/limits.html
> e.g. after "columns per table".
>
> We've generally felt that the existing "columns per table" limit is
> sufficient detail here.
>
ISTM that adding detail is free whereas the readers time to figure out why
and where this number came from is not.
I think it deserves mention.
Regards,
Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zhihong Yu | 2022-05-31 14:31:35 | Re: adding status for COPY progress report |
| Previous Message | Tom Lane | 2022-05-31 14:16:45 | Re: PostgreSQL Limits: maximum number of columns in SELECT result |