diff options
| author | David Rowley <drowley@postgresql.org> | 2022-06-01 12:46:54 +1200 |
|---|---|---|
| committer | David Rowley <drowley@postgresql.org> | 2022-06-01 12:46:54 +1200 |
| commit | e6bd7aafc82d5f7ae1cb4bf15ce47d2ad12e5dd3 (patch) | |
| tree | ba758a0e67506ff70d9edb1a158554f293323e56 | |
| parent | c73748b68a0e5f80d9014af748b194f728a074d3 (diff) | |
| download | postgresql-e6bd7aafc82d5f7ae1cb4bf15ce47d2ad12e5dd3.tar.gz postgresql-e6bd7aafc82d5f7ae1cb4bf15ce47d2ad12e5dd3.zip | |
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
| -rw-r--r-- | doc/src/sgml/limits.sgml | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/src/sgml/limits.sgml b/doc/src/sgml/limits.sgml index 7713ff71773..d5b2b627ddf 100644 --- a/doc/src/sgml/limits.sgml +++ b/doc/src/sgml/limits.sgml @@ -63,6 +63,12 @@ </row> <row> + <entry>columns in a result set</entry> + <entry>1664</entry> + <entry></entry> + </row> + + <row> <entry>field size</entry> <entry>1 GB</entry> <entry></entry> |