diff options
| author | David Rowley <drowley@postgresql.org> | 2022-06-01 12:44:45 +1200 |
|---|---|---|
| committer | David Rowley <drowley@postgresql.org> | 2022-06-01 12:44:45 +1200 |
| commit | bbb6489042a8928ccba7d72343b9ea6d0c607974 (patch) | |
| tree | cedeebcc07644e46df272275d62e1f674ebd51f1 /src/backend/executor/nodeProjectSet.c | |
| parent | e1ed1a7aa5477a52faad2699c881966fb73128cb (diff) | |
| download | postgresql-bbb6489042a8928ccba7d72343b9ea6d0c607974.tar.gz postgresql-bbb6489042a8928ccba7d72343b9ea6d0c607974.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
Diffstat (limited to 'src/backend/executor/nodeProjectSet.c')
0 files changed, 0 insertions, 0 deletions