Value | Meaning |
---|---|
NULL0 | |
BOOLEAN16 | |
BYTEA17 | |
CHARACTER18 | |
NAME19 | |
BIGINT20 | int8 |
SMALLINT21 | int2 |
INT23 | int4 |
TEXT25 | |
OID26 | |
TID27 | |
XID28 | |
CID29 | |
PG_TYPE71 | |
JSON114 | |
XML142 | |
POINT600 | |
PATH602 | |
BOX603 | |
POLYGON604 | |
LINE628 | |
CIDR650 | |
REAL700 | 32-bit float |
DOUBLE701 | 64-bit double, is actually called 'double precision' |
ABSTIME702 | |
UNKNOWN705 | |
CIRCLE718 | |
MONEY790 | |
INET869 | |
VARCHAR1043 | |
DATE1082 | |
TIME1083 | |
TIMESTAMP1114 | |
INTERVAL1186 | |
TIMETZ1266 | |
BIT1560 | |
VARBIT1562 | |
NUMERIC1700 | |
VOID2278 | "Another special case is that a parameter's type can be specified as void (that is, the OID of the void pseudo-type). This is meant to allow parameter symbols to be used for function parameters that are actually OUT parameters. Ordinarily there is no context in which a void parameter could be used, but if such a parameter symbol appears in a function's parameter list, it is effectively ignored. For example, a function call such as foo($1,$2,$3,$4) could match a function with two IN and two OUT arguments, if $3 and $4 are specified as having type void." |
UUID2950 | |
JSONB3802 |
Small portion of statically known ids of Psql types, wich is enough to start connection and request full type list.