diff options
author | Bruce Momjian | 2023-10-31 13:23:09 +0000 |
---|---|---|
committer | Bruce Momjian | 2023-10-31 13:23:09 +0000 |
commit | 4a6286fd939e84b894f074586e522b7102fc53c5 (patch) | |
tree | 506e5fbe0ffbe60f6b0f81239bf7882c4f01795f | |
parent | 989adace3f19010f21009477afb5b50e1a4dd3c6 (diff) |
doc: add function argument and query parameter limits
Also reorder entries and add commas.
Reported-by: David G. Johnston
Discussion: https://postgr.es/m/CAKFQuwYeNPxeocV3_0+Zx=_Xwvg+sNyEMdzyG5s2E2e0hZLQhg@mail.gmail.com
Author: David G. Johnston (partial)
Backpatch-through: 12
-rw-r--r-- | doc/src/sgml/limits.sgml | 42 |
1 files changed, 27 insertions, 15 deletions
diff --git a/doc/src/sgml/limits.sgml b/doc/src/sgml/limits.sgml index d5b2b627ddf..c549447013f 100644 --- a/doc/src/sgml/limits.sgml +++ b/doc/src/sgml/limits.sgml @@ -57,14 +57,14 @@ <row> <entry>columns per table</entry> - <entry>1600</entry> + <entry>1,600</entry> <entry>further limited by tuple size fitting on a single page; see note below</entry> </row> <row> <entry>columns in a result set</entry> - <entry>1664</entry> + <entry>1,664</entry> <entry></entry> </row> @@ -75,12 +75,6 @@ </row> <row> - <entry>identifier length</entry> - <entry>63 bytes</entry> - <entry>can be increased by recompiling <productname>PostgreSQL</productname></entry> - </row> - - <row> <entry>indexes per table</entry> <entry>unlimited</entry> <entry>constrained by maximum relations per database</entry> @@ -92,11 +86,29 @@ <entry>can be increased by recompiling <productname>PostgreSQL</productname></entry> </row> - <row> - <entry>partition keys</entry> - <entry>32</entry> - <entry>can be increased by recompiling <productname>PostgreSQL</productname></entry> - </row> + <row> + <entry>partition keys</entry> + <entry>32</entry> + <entry>can be increased by recompiling <productname>PostgreSQL</productname></entry> + </row> + + <row> + <entry>identifier length</entry> + <entry>63 bytes</entry> + <entry>can be increased by recompiling <productname>PostgreSQL</productname></entry> + </row> + + <row> + <entry>function arguments</entry> + <entry>100</entry> + <entry>can be increased by recompiling <productname>PostgreSQL</productname></entry> + </row> + + <row> + <entry>query parameters</entry> + <entry>65,535</entry> + <entry></entry> + </row> </tbody> </tgroup> </table> @@ -104,9 +116,9 @@ <para> The maximum number of columns for a table is further reduced as the tuple being stored must fit in a single 8192-byte heap page. For example, - excluding the tuple header, a tuple made up of 1600 <type>int</type> columns + excluding the tuple header, a tuple made up of 1,600 <type>int</type> columns would consume 6400 bytes and could be stored in a heap page, but a tuple of - 1600 <type>bigint</type> columns would consume 12800 bytes and would + 1,600 <type>bigint</type> columns would consume 12800 bytes and would therefore not fit inside a heap page. Variable-length fields of types such as <type>text</type>, <type>varchar</type>, and <type>char</type> |