| From: | David Rowley <drowley(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Doc: mention limitation of the number of resultset columns |
| Date: | 2022-06-01 00:46:08 |
| Message-ID: | E1nwCUx-0026l1-PI@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Doc: mention limitation of the number of resultset columns
The PostgreSQL limitations section of the documents mentioned the limit
on the number of columns that can exist in a table. Users might be
surprised to find that there's also a limit on the number of columns that
can exist in a targetlist. Users may experience restrictions which
surprise them if they happened to select a large number of columns from
several tables with many columns. Here we document that there is a
limitation on this and mention what that limit actually is.
Wording proposal by Alvaro Herrera
Reported-by: Vladimir Sitnikov
Author: Dave Crammer
Reviewed-by: Tom Lane
Discussion: https://postgr.es/m/CAB=Je-E18aTYpNqje4mT0iEADpeGLSzwUvo3H9kRRuDdsNo4aQ@mail.gmail.com
Backpatch-through: 12, where the limitations section was added
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/bbb6489042a8928ccba7d72343b9ea6d0c607974
Modified Files
--------------
doc/src/sgml/limits.sgml | 6 ++++++
1 file changed, 6 insertions(+)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2022-06-01 00:46:44 | pgsql: Doc: mention limitation of the number of resultset columns |
| Previous Message | Magnus Hagander | 2022-05-31 20:03:19 | pgsql: Recommend scram-sha-256 instead of md5 authentication in docs |