The catalog pg_shseclabel stores security
- lables on shared database objects. Security labels can be manipulated
+ labels on shared database objects. Security labels can be manipulated
with the command. For an easier
way to view security labels, see .
column. bigserial should be used if you anticipate
the use of more than 231> identifiers over the
lifetime of the table. The type names smallserial and
- serial2 also work the same way, execpt that they
+ serial2 also work the same way, except that they
create a smallint column.
On , getattr> permission
will be checked on the source or template database of the new database,
not only create> on the new database.
- On creation of objects within a particula schema (tables, views,
- sequences and procedures), add_name> will be also chechked
+ On creation of objects within a particular schema (tables, views,
+ sequences and procedures), add_name> will be also checked
on the schema, not only create> on the new object itself.
to switch the security label of the client process, the client domain,
to a new context, if that is allowed by the security policy.
The client domain needs the setcurrent> permission and also
- dyntransaction> from the old to the new domain.
+ dyntransition> from the old to the new domain.
Dynamic domain transitions should be considered carefully, because they
|
sepgsql_restorecon(text) returns bool
- Sets up initial security labels for all objectes within the
+ Sets up initial security labels for all objects within the
current database. The argument may be NULL, or the name of a specfile
to be used as alternative of the system default.
for primary key columns. Each part is separated from the next by a comma.
For ease of parsing using regular expressions, table and column names are
always wrapped in double quotes, and data values are always wrapped in
- single quotes. Embeded quotes are doubled.
+ single quotes. Embedded quotes are doubled.