|
-
- array_cat
- (anyarray, anyarray)
-
-
- anyarray
- concatenate two arrays
- array_cat(ARRAY[1,2,3], ARRAY[4,5])
- {1,2,3,4,5}
-
- |
-
array_append
(anyarray, anyelement)
|
- array_prepend
- (anyelement, anyarray)
+ array_cat
+ (anyarray, anyarray)
anyarray
- append an element to the beginning of an array
- array_prepend(1, ARRAY[2,3])
- {1,2,3}
+ concatenate two arrays
+ array_cat(ARRAY[1,2,3], ARRAY[4,5])
+ {1,2,3,4,5}
|
|
- array_upper
- (anyarray, int)
+ array_prepend
+ (anyelement, anyarray)
- int
- returns upper bound of the requested array dimension
- array_upper(ARRAY[1,2,3,4], 1)
- 4
+ anyarray
+ append an element to the beginning of an array
+ array_prepend(1, ARRAY[2,3])
+ {1,2,3}
|
|
+
+ array_upper
+ (anyarray, int)
+
+
+ int
+ returns upper bound of the requested array dimension
+ array_upper(ARRAY[1,2,3,4], 1)
+ 4
+
+ |
+
string_to_array
(text, text)
port of the local connection
- |
- session_user
- name
- session user name
-
-
|
pg_postmaster_start_time()
timestamp with time zone
server start time
+ |
+ session_user
+ name
+ session user name
+
+
|
user
name
- |
-
has_table_privilege(user,
-
- boolean
- does user have privilege for table
-
- |
-
has_table_privilege(table,
-
- boolean
- does current user have privilege for table
-
|
has_database_privilege(user,
does current user have privilege for language
|
+
has_schema_privilege(user,
boolean
- does user have privilege for role
+ does user have privilege for schema
|
+
has_schema_privilege(schema,
boolean
- does current user have privilege for role
+ does current user have privilege for schema
|
-
has_schema_privilege(user,
+
has_table_privilege(user,
boolean
- does user have privilege for schema
+ does user have privilege for table
|
-
has_schema_privilege(schema,
+
has_table_privilege(table,
boolean
- does current user have privilege for schema
+ does current user have privilege for table
|
has_tablespace_privilege(user,
boolean
does current user have privilege for tablespace
+ |
+
+ boolean
+ does user have privilege for role
+
+ |
+
+ boolean
+ does current user have privilege for role
+
-
-
-
- has_table_privilege checks whether a user
- can access a table in a particular way. The user can be
- specified by name or by OID
- (pg_authid.oid), or if the argument is
- omitted
- current_user is assumed. The table can be specified
- by name or by OID. (Thus, there are actually six variants of
- has_table_privilege, which can be distinguished by
- the number and types of their arguments.) When specifying by name,
- the name can be schema-qualified if necessary.
- The desired access privilege type
- is specified by a text string, which must evaluate to one of the
- values SELECT, INSERT, UPDATE,
- DELETE, RULE, REFERENCES, or
- TRIGGER. (Case of the string is not significant, however.)
- An example is:
-SELECT has_table_privilege('myschema.mytable', 'select');
-
-
+
+
has_database_privilege checks whether a user
USAGE.
- pg_has_role checks whether a user
- can access a role in a particular way. The possibilities for its
- arguments are analogous to has_table_privilege.
- The desired access privilege type must evaluate to
- MEMBER or
- USAGE.
- MEMBER denotes direct or indirect membership in
- the role (that is, the right to do SET ROLE>), while
- USAGE denotes whether the privileges of the role
- are immediately available without doing SET ROLE>.
-
-
has_schema_privilege checks whether a user
can access a schema in a particular way. The possibilities for its
USAGE.
+ has_table_privilege checks whether a user
+ can access a table in a particular way. The user can be
+ specified by name or by OID
+ (pg_authid.oid), or if the argument is
+ omitted
+ current_user is assumed. The table can be specified
+ by name or by OID. (Thus, there are actually six variants of
+ has_table_privilege, which can be distinguished by
+ the number and types of their arguments.) When specifying by name,
+ the name can be schema-qualified if necessary.
+ The desired access privilege type
+ is specified by a text string, which must evaluate to one of the
+ values SELECT, INSERT, UPDATE,
+ DELETE, RULE, REFERENCES, or
+ TRIGGER. (Case of the string is not significant, however.)
+ An example is:
+SELECT has_table_privilege('myschema.mytable', 'select');
+
+
+
has_tablespace_privilege checks whether a user
can access a tablespace in a particular way. The possibilities for its
CREATE.
+ pg_has_role checks whether a user
+ can access a role in a particular way. The possibilities for its
+ arguments are analogous to has_table_privilege.
+ The desired access privilege type must evaluate to
+ MEMBER or
+ USAGE.
+ MEMBER denotes direct or indirect membership in
+ the role (that is, the right to do SET ROLE>), while
+ USAGE denotes whether the privileges of the role
+ are immediately available without doing SET ROLE>.
+
+
To test whether a user holds a grant option on the privilege,
- append WITH GRANT OPTION to the privilege key
+ append WITH GRANT OPTION to the privilege key
word; for example 'UPDATE WITH GRANT OPTION'.
|
-
pg_table_is_visible(table_oid)
-
- boolean
- is table visible in search path
-
- |
-
pg_type_is_visible(type_oid)
+
pg_conversion_is_visible(conversion_oid)
boolean
- is type (or domain) visible in search path
+ is conversion visible in search path
|
pg_function_is_visible(function_oid)
is operator class visible in search path
|
-
pg_conversion_is_visible(conversion_oid)
+
pg_table_is_visible(table_oid)
boolean
- is conversion visible in search path
+ is table visible in search path
+
+ |
+
pg_type_is_visible(type_oid)
+
+ boolean
+ is type (or domain) visible in search path
-
-
+
pg_conversion_is_visible
-
pg_conversion_is_visible
+
+
- pg_table_is_visible performs the check for
- tables (or views, or any other kind of pg_class> entry).
- pg_type_is_visible,
- pg_function_is_visible,
- pg_operator_is_visible,
- pg_opclass_is_visible, and
- pg_conversion_is_visible perform the same sort of
- visibility check for types (and domains), functions, operators, operator classes
- and conversions, respectively. For functions and operators, an object in
- the search path is visible if there is no object of the same name
- and argument data type(s)> earlier in the path. For
- operator classes, both name and associated index access method are
- considered.
+ pg_conversion_is_visible,
+ pg_function_is_visible,
+ pg_operator_is_visible,
+ pg_opclass_is_visible,
+ pg_table_is_visible, and
+ pg_type_is_visible perform the visibility check for
+ conversions, functions, operators, operator classes, tables, and
+ types. Note that pg_table_is_visible can also be used
+ with views, indexes and sequences; pg_type_is_visible
+ can also be used with domains. For functions and operators, an object in
+ the search path is visible if there is no object of the same name
+ and argument data type(s)> earlier in the path. For operator
+ classes, both name and associated index access method are considered.
get name of the sequence that a serial or bigserial column
uses
- |
-
pg_tablespace_databases(tablespace_oid)
- setof oid
- get the set of database OIDs that have objects in the tablespace
-
|
pg_get_triggerdef(trigger_oid)
text
text
get underlying SELECT command for view
+ |
+
pg_tablespace_databases(tablespace_oid)
+ setof oid
+ get the set of database OIDs that have objects in the tablespace
+