aboutsummaryrefslogtreecommitdiff
path: root/src/tutorial/funcs.c
diff options
context:
space:
mode:
authorDavid Rowley <drowley@postgresql.org>2022-06-01 12:46:18 +1200
committerDavid Rowley <drowley@postgresql.org>2022-06-01 12:46:18 +1200
commitf2a0060a9bfb7a6f257a536de5ea2d4f7cedff03 (patch)
tree27a21fe565b24208ac5f11f2fae8be53f39c6384 /src/tutorial/funcs.c
parenta694cf4ca496a7db66a61f6ec2a15a9af6493cef (diff)
downloadpostgresql-f2a0060a9bfb7a6f257a536de5ea2d4f7cedff03.tar.gz
postgresql-f2a0060a9bfb7a6f257a536de5ea2d4f7cedff03.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/tutorial/funcs.c')
0 files changed, 0 insertions, 0 deletions