|
columns per table
- 1600
+ 1,600
further limited by tuple size fitting on a single page; see note
below
|
columns in a result set
- 1664
+ 1,664
- |
- identifier length
- 63 bytes
-
can be increased by recompiling PostgreSQL
-
-
|
indexes per table
unlimited
can be increased by recompiling PostgreSQL
- |
- partition keys
- 32
-
can be increased by recompiling PostgreSQL
-
+ |
+ partition keys
+ 32
+
can be increased by recompiling PostgreSQL
+
+
+ |
+ identifier length
+ 63 bytes
+
can be increased by recompiling PostgreSQL
+
+
+ |
+ function arguments
+ 100
+
can be increased by recompiling PostgreSQL
+
+
+ |
+ query parameters
+ 65,535
+
+
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 int columns
+ excluding the tuple header, a tuple made up of 1,600 int columns
would consume 6400 bytes and could be stored in a heap page, but a tuple of
- 1600 bigint columns would consume 12800 bytes and would
+ 1,600 bigint columns would consume 12800 bytes and would
therefore not fit inside a heap page.
Variable-length fields of
types such as text, varchar, and char