aboutsummaryrefslogtreecommitdiff
path: root/src/backend/tcop/postgres.c
diff options
context:
space:
mode:
authorDavid Rowley <drowley@postgresql.org>2022-06-01 12:47:27 +1200
committerDavid Rowley <drowley@postgresql.org>2022-06-01 12:47:27 +1200
commit9ae467db92ce8e26b0c3d37f79926f0174b70864 (patch)
tree2048b70ae8ee4cbbcb12472cd259086c765b78bc /src/backend/tcop/postgres.c
parenta3faebd6a58aaff0d6521428831041d517db62fe (diff)
downloadpostgresql-9ae467db92ce8e26b0c3d37f79926f0174b70864.tar.gz
postgresql-9ae467db92ce8e26b0c3d37f79926f0174b70864.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/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions