+ linkend="sql-createdatabase" endterm="sql-createdatabase-title"> command.
+ Consult for details about the meaning
+ of some of the parameters.
If true then this database can be used in the
TEMPLATE clause of CREATE
DATABASE to create a new database as a clone of
- this one.
+ this one
If false then no one can connect to this database. This is
- used to protect the template0> database from being altered.
+ used to protect the template0> database from being altered
Sets maximum number of concurrent connections that can be made
- to this database. -1 means no limit.
+ to this database. -1 means no limit
track whether the database needs to be vacuumed in order to prevent
transaction ID wraparound or to allow pg_clog> to be shrunk.
It is the minimum of the per-table
- pg_class>.relfrozenxid> values.
+ pg_class>.relfrozenxid> values
Within this database, all tables for which
pg_class>.reltablespace> is zero
will be stored in this tablespace; in particular, all the non-shared
- system catalogs will be there.
+ system catalogs will be there
For a table column, this is the column number (the
objid> and classid> refer to the
table itself). For all other object types, this column is
- zero.
+ zero
For a table column, this is the column number (the
refobjid> and refclassid> refer
to the table itself). For all other object types, this column
- is zero.
+ is zero
The catalog pg_description> stores optional descriptions
(comments) for each database object. Descriptions can be manipulated
- with the <command>COMMENT> command and viewed with
+ with the <xref linkend="sql-comment" endterm="sql-comment-title" > command and viewed with
Descriptions of many built-in system objects are provided in the initial
contents of pg_description .
For a comment on a table column, this is the column number (the
objoid> and classoid> refer to
the table itself). For all other object types, this column is
- zero.
+ zero
indisvalid
bool
- If true, the index is currently valid for queries.
- False means the index is possibly incomplete: it must still be
- inserted into by INSERT/UPDATE operations, but it cannot safely be
- used for queries, and if it is unique, the uniqueness shouldn't be
- relied on either.
+
+ If true, the index is currently valid for queries. False means the
+ index is possibly incomplete: it must still be modified by
+ INSERT>/UPDATE> operations, but it cannot safely
+ be used for queries. If it is unique, the uniqueness property is not
+ true either
+
|
For each column in the index key this contains the OID of
the operator class to use. See
- <structname>pg_opclass for details.
+ <link linkend="catalog-pg-opclass">pg_opclass for details
Expression trees (in nodeToString() representation)
for index attributes that are not simple column references. This is a
list with one element for each zero entry in indkey>.
- NULL if all index attributes are simple references.
+ NULL if all index attributes are simple references
|
text
Expression tree (in nodeToString() representation)
- for partial index predicate. NULL if not a partial index.
+ for partial index predicate. NULL if not a partial index
If there is more than one direct parent for a child table (multiple
inheritance), this number tells the order in which the
- inherited columns are to be arranged. The count starts at 1.
+ inherited columns are to be arranged. The count starts at 1
SQL ) and true for user-defined languages.
Currently,
pg_dump still uses this
to determine which languages need to be dumped, but this may be
- replaced by a different mechanism sometime.
+ replaced by a different mechanism in the future
True if this is a trusted language, which means that it is believed
not to grant access to anything outside the normal SQL execution
environment. Only superusers may create functions in untrusted
- languages.
+ languages
For noninternal languages this references the language
handler, which is a special function that is responsible for
executing all functions that are written in the particular
- language.
+ language
This references a language validator function that is responsible
for checking the syntax and validity of new functions when they
- are created. Zero if no validator is provided.
+ are created. Zero if no validator is provided
OID assigned when it is created. Each large object is broken into
segments or pages> small enough to be conveniently stored as rows
in pg_largeobject .
- The amount of data per page is defined to be <litera l>LOBLKSIZE> (which is currently
+ The amount of data per page is defined to be <symbo l>LOBLKSIZE> (which is currently
BLCKSZ/4>, or typically 2 kB).
|
Name
Type
- References
Description
|
loid
oid
-
Identifier of the large object that includes this page
|
pageno
int4
-
Page number of this page within its large object
(counting from zero)
|
data
bytea
-
Actual data stored in the large object.
- This will never be more than LOBLKSIZE> bytes and may be less.
+ This will never be more than LOBLKSIZE> bytes and may be less
|
relname
name
-
- Notify condition name. (The name need not match any actual
- relation in the database; the name relname> is historical.)
+
+ Notify condition name. (The name need not match any actual
+ relation in the database; the name relname> is historical.)
|
listenerpid
int4
-
PID of the server process that created this entry
|
notification
int4
-
Zero if no event is pending for this listener. If an event is
- pending, the PID of the server process that sent the notification.
+ pending, the PID of the server process that sent the notification
|
Name
Type
- References
Description
|
tmplname
name
-
Name of the language this template is for
|
tmpltrusted
boolean
-
True if language is considered trusted
|
tmplhandler
text
-
Name of call handler function
|
tmplvalidator
text
-
Name of validator function, or NULL if none
|
tmpllibrary
text
-
Path of shared library that implements language
|
tmplacl
aclitem[]
-
Access privileges for template (not yet used)
Function returns null if any call argument is null. In that
case the function won't actually be called at all. Functions
that are not strict
must be prepared to handle
- null inputs.
+ null inputs
An array with the data types of the function arguments. This includes
only input arguments (including INOUT arguments), and thus represents
- the call signature of the function.
+ the call signature of the function
all arguments (including OUT and INOUT arguments); however, if all the
arguments are IN arguments, this field will be null.
Note that subscripting is 1-based, whereas for historical reasons
- proargtypes> is subscripted from 0.
+ proargtypes> is subscripted from 0
b for INOUT> arguments.
If all the arguments are IN arguments, this field will be null.
Note that subscripts correspond to positions of
- proallargtypes> not proargtypes>.
+ proallargtypes> not proargtypes>
Arguments without a name are set to empty strings in the array.
If none of the arguments have a name, this field will be null.
Note that subscripts correspond to positions of
- proallargtypes> not proargtypes>.
+ proallargtypes> not proargtypes>
This tells the function handler how to invoke the function. It
might be the actual source code of the function for interpreted
languages, a link symbol, a file name, or just about anything
- else, depending on the implementation language/call convention.
+ else, depending on the implementation language/call convention
probin
bytea
- Additional information about how to invoke the function.
- Again, the interpretation is language-specific.
+
+ Additional information about how to invoke the function.
+ Again, the interpretation is language-specific
The catalog pg_shdescription stores optional
- descriptions (comments) for shared database objects. Descriptions can
- be manipulated with the COMMENT command and viewed
- with
psql 's
\d commands.
+ descriptions (comments) for shared database objects. Descriptions can be
+ manipulated with the
+ endterm="sql-comment-title"> command and viewed with
description
text
- Arbitrary text that servers as the description of this object.
+ Arbitrary text that serves as the description of this object
A value less than zero is the negative of a fraction of the number
of rows in the table (for example, a column in which values appear about
twice on the average could be represented by stadistinct> = -0.5).
- A zero value means the number of distinct values is unknown.
+ A zero value means the number of distinct values is unknown
A code number indicating the kind of statistics stored in the
N>th slot
of the
- pg_statistic row.
+ pg_statistic row
An operator used to derive the statistics stored in the
N>th slot
. For example, a
histogram slot would show the < operator
- that defines the sort order of the data.
+ that defines the sort order of the data
kind does not store any data values. Each array's element
values are actually of the specific column's data type, so there
is no way to define these columns' type more specifically than
- anyarray>.
+ anyarray>
Variable-length types are always passed by reference. Note that
typbyval can be false even if the
length would allow pass-by-value; this is currently true for
- type float4 , for example.
+ type float4 , for example
table's row type), d for a domain, or
p for a pseudo-type. See also
typrelid and
- typbasetype .
+ typbasetype
True if the type is defined, false if this is a placeholder
entry for a not-yet-defined type. When
typisdefined is false, nothing
- except the type name, namespace, and OID can be relied on.
+ except the type name, namespace, and OID can be relied on
typdelim
char
- Character that separates two values of this type when parsing
- array input. Note that the delimiter is associated with the array
- element data type, not the array data type.
+
+ Character that separates two values of this type when parsing
+ array input. Note that the delimiter is associated with the array
+ element data type, not the array data type
+
|
pg_class entry doesn't really represent
a table, but it is needed anyway for the type's
pg_attribute entries to link to.)
- Zero for non-composite types.
+ Zero for non-composite types
its internal representation must be some number of values of the
typelem data type with no other data.
Variable-length array types have a header defined by the array
- subroutines.
+ subroutines
typnotnull represents a not-null
- constraint on a type. Used for domains only.
+ constraint on a type. Used for domains only
oid
pg_type .oid
- If this is a domain (see typtype ),
- then typbasetype identifie s
- the type that this one is based on. Zero if not a domain.
+ If this is a domain (see typtype ), then
+ typbasetype identifies the type that thi s
+ one is based on. Zero if this type is not a domain
Domains use typtypmod to record the typmod>
to be applied to their base type (-1 if base type does not use a
- typmod>). -1 if this type is not a domain.
+ typmod>). -1 if this type is not a domain
typndims is the number of array dimensions
for a domain that is an array (that is, typbasetype> is an array type;
the domain's typelem> will match the base type's typelem ).
- Zero for types other than array domains.
+ Zero for types other than array domains
If typdefaultbin> is not null, it is the nodeToString()
representation of a default expression for the type. This is
- only used for domains.
+ only used for domains
typdefaultbin> is null and typdefault> is
not, then typdefault> is the external representation of
the type's default value, which may be fed to the type's input
- converter to produce a constant.
+ converter to produce a constant
|
Name
Type
- References
Description
|
name
text
-
The name of the cursor
|
statement
text
-
The verbatim query string submitted to declare this cursor
|
is_holdable
boolean
-
true if the cursor is holdable (that is, it
can be accessed after the transaction that declared the cursor
|
is_binary
boolean
-
true if the cursor was declared
BINARY ; false
|
is_scrollable
boolean
-
true> if the cursor is scrollable (that is, it
allows rows to be retrieved in a nonsequential manner);
|
creation_time
timestamptz
-
The time at which the cursor was declared
schemaname
name
pg_namespace .nspname
- n ame of schema containing table and index
+ N ame of schema containing table and index
|
tablename
name
pg_class .relname
- n ame of table the index is for
+ N ame of table the index is for
|
indexname
name
pg_class .relname
- n ame of index
+ N ame of index
|
tablespace
name
pg_tablespace .spcname
- n ame of tablespace containing index (NULL if default for database)
+ N ame of tablespace containing index (NULL if default for database)
|
indexdef
text
- index definition (a reconstructed creation command)
+ Index definition (a reconstructed CREATE INDEX
+ command)
integer
- p age number within the relation, or NULL if the object
+ P age number within the relation, or NULL if the object
is not a tuple or relation page
smallint
- t uple number within the page, or NULL if the object is not a tuple
+ T uple number within the page, or NULL if the object is not a tuple
|
Process ID of the server process holding or awaiting this
- lock. NULL if the lock is held by a prepared transaction.
+ lock. NULL if the lock is held by a prepared transaction
|
mode
text
-
n ame of the lock mode held or desired by this process (see
+
N ame of the lock mode held or desired by this process (see
linkend="locking-tables">)
|
granted
boolean
- t rue if lock is held, false if lock is awaited
+ T rue if lock is held, false if lock is awaited
view produces a consistent set of results, while not blocking
normal lock manager operations longer than necessary. Nonetheless
there could be some impact on database performance if this view is
- read often .
+ frequently accessed .
|
Name
Type
- References
Description
|
name
text
-
The identifier of the prepared statement
|
statement
text
-
The query string submitted by the client to create this
prepared statement. For prepared statements created via SQL,
this is the PREPARE statement submitted by
the client. For prepared statements created via the
frontend/backend protocol, this is the text of the prepared
- statement itself.
+ statement itself
|
prepare_time
timestamptz
-
The time at which the prepared statement was created
|
parameter_types
regtype[]
-
The expected parameter types for the prepared statement in the
form of an array of regtype . The OID corresponding
to an element of this array can be obtained by casting the
- regtype value to oid .
+ regtype value to oid
|
from_sql
boolean
-
true if the prepared statement was created
via the PREPARE SQL statement;
view produces a consistent set of results, while not blocking
normal operations longer than necessary. Nonetheless
there could be some impact on database performance if this view is
- read often .
+ frequently accessed .
bool
- Role may log in, t hat is, this role can be given as the initial
- session authorization identifier.
+ Role may log in. T hat is, this role can be given as the initial
+ session authorization identifier
For roles that can log in, this sets maximum number of concurrent
- connections this role can make. -1 means no limit.
+ connections this role can make. -1 means no limit
schemaname
name
pg_namespace .nspname
- n ame of schema containing table
+ N ame of schema containing table
|
tablename
name
pg_class .relname
- n ame of table the rule is for
+ N ame of table the rule is for
|
rulename
name
pg_rewrite .rulename
- n ame of rule
+ N ame of rule
|
definition
text
- r ule definition (a reconstructed creation command)
+ R ule definition (a reconstructed creation command)