From 5e45211a64149b3c659b90ff2de6fa982a5a93ed Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:17:33 +0200 Subject: Adding upstream version 15.5. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/bki-commands.html | 111 ++++++++++++++++++++++++++++++++++++ 1 file changed, 111 insertions(+) create mode 100644 doc/src/sgml/html/bki-commands.html (limited to 'doc/src/sgml/html/bki-commands.html') diff --git a/doc/src/sgml/html/bki-commands.html b/doc/src/sgml/html/bki-commands.html new file mode 100644 index 0000000..2809143 --- /dev/null +++ b/doc/src/sgml/html/bki-commands.html @@ -0,0 +1,111 @@ + +74.4. BKI Commands

74.4. BKI Commands

+ create + tablename + tableoid + [bootstrap] + [shared_relation] + [rowtype_oid oid] + (name1 = + type1 + [FORCE NOT NULL | FORCE NULL ] [, + name2 = + type2 + [FORCE NOT NULL | FORCE NULL ], + ...]) +

+ Create a table named tablename, and having the OID + tableoid, + with the columns given in parentheses. +

+ The following column types are supported directly by + bootstrap.c: bool, + bytea, char (1 byte), + name, int2, + int4, regproc, regclass, + regtype, text, + oid, tid, xid, + cid, int2vector, oidvector, + _int4 (array), _text (array), + _oid (array), _char (array), + _aclitem (array). Although it is possible to create + tables containing columns of other types, this cannot be done until + after pg_type has been created and filled with + appropriate entries. (That effectively means that only these + column types can be used in bootstrap catalogs, but non-bootstrap + catalogs can contain any built-in type.) +

+ When bootstrap is specified, + the table will only be created on disk; nothing is entered into + pg_class, + pg_attribute, etc., for it. Thus the + table will not be accessible by ordinary SQL operations until + such entries are made the hard way (with insert + commands). This option is used for creating + pg_class etc. themselves. +

+ The table is created as shared if shared_relation is + specified. + The table's row type OID (pg_type OID) can optionally + be specified via the rowtype_oid clause; if not specified, + an OID is automatically generated for it. (The rowtype_oid + clause is useless if bootstrap is specified, but it can be + provided anyway for documentation.) +

+ open tablename +

+ Open the table named + tablename + for insertion of data. Any currently open table is closed. +

+ close tablename +

+ Close the open table. The name of the table must be given as a + cross-check. +

+ insert ( [oid_value] value1 value2 ... ) +

+ Insert a new row into the open table using value1, value2, etc., for its column + values. +

+ NULL values can be specified using the special key word + _null_. Values that do not look like + identifiers or digit strings must be single-quoted. + (To include a single quote in a value, write it twice. + Escape-string-style backslash escapes are allowed in the string, too.) +

+ declare [unique] + index indexname + indexoid + on tablename + using amname + ( opclass1 + name1 + [, ...] ) +

+ Create an index named indexname, having OID + indexoid, + on the table named + tablename, using the + amname access + method. The fields to index are called name1, name2 etc., and the operator + classes to use are opclass1, opclass2 etc., respectively. + The index file is created and appropriate catalog entries are + made for it, but the index contents are not initialized by this command. +

+ declare toast + toasttableoid + toastindexoid + on tablename +

+ Create a TOAST table for the table named + tablename. + The TOAST table is assigned OID + toasttableoid + and its index is assigned OID + toastindexoid. + As with declare index, filling of the index + is postponed. +

build indices

+ Fill in the indices that have previously been declared. +

\ No newline at end of file -- cgit v1.2.3