aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistutil.c
diff options
context:
space:
mode:
authorDavid Rowley <drowley@postgresql.org>2022-06-01 12:44:45 +1200
committerDavid Rowley <drowley@postgresql.org>2022-06-01 12:44:45 +1200
commitbbb6489042a8928ccba7d72343b9ea6d0c607974 (patch)
treecedeebcc07644e46df272275d62e1f674ebd51f1 /src/backend/access/gist/gistutil.c
parente1ed1a7aa5477a52faad2699c881966fb73128cb (diff)
downloadpostgresql-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/access/gist/gistutil.c')
0 files changed, 0 insertions, 0 deletions