revocation list (CRL). Certificates listed in this file, if it
exists, will be rejected while attempting to authenticate the
server's certificate. If neither
- 'libpq-connect-sslcrl'/> nor
- 'libpq-connect-sslcrldir'/> is set, this setting is
+ "libpq-connect-sslcrl"/> nor
+ "libpq-connect-sslcrldir"/> is set, this setting is
taken as
~/.postgresql/root.crl.
pg_stat_progress_analyzepg_stat_progress_analyze
One row for each backend (including autovacuum worker processes) running
ANALYZE, showing current progress.
- See 'analyze-progress-reporting'/>.
+ See "analyze-progress-reporting"/>.
pg_stat_progress_create_indexpg_stat_progress_create_index
One row for each backend running CREATE INDEX or REINDEX, showing
current progress.
- See 'create-index-progress-reporting'/>.
+ See "create-index-progress-reporting"/>.
pg_stat_progress_vacuumpg_stat_progress_vacuum
One row for each backend (including autovacuum worker processes) running
VACUUM, showing current progress.
- See 'vacuum-progress-reporting'/>.
+ See "vacuum-progress-reporting"/>.
pg_stat_progress_clusterpg_stat_progress_cluster
One row for each backend running
CLUSTER or VACUUM FULL, showing current progress.
- See 'cluster-progress-reporting'/>.
+ See "cluster-progress-reporting"/>.
pg_stat_progress_basebackuppg_stat_progress_basebackup
One row for each WAL sender process streaming a base backup,
showing current progress.
- See 'basebackup-progress-reporting'/>.
+ See "basebackup-progress-reporting"/>.
|
pg_stat_progress_copypg_stat_progress_copy
One row for each backend running COPY, showing current progress.
- See 'copy-progress-reporting'/>.
+ See "copy-progress-reporting"/>.
pg_stat_progress_cluster
because both VACUUM FULL and CLUSTER
rewrite the table, while regular VACUUM only modifies it
- in place. See 'cluster-progress-reporting'/>.
+ in place. See "cluster-progress-reporting"/>.
These clauses determine whether a role will be permitted to
create, alter, drop, comment on, and change the security label for
other roles.
- See 'role-creation' /> for more details about what
+ See "role-creation"/> for more details about what
capabilities are conferred by this privilege.
If not specified, NOCREATEROLE is the default.
Being a superuser implies the ability to bypass all access permission
checks within the database, so superuser access should not be granted
lightly. CREATEROLE also conveys
- 'role-creation'>very extensive privileges.
+ "role-creation">very extensive privileges.
The new user will be allowed to create, alter, drop, comment on,
change the security label for other roles; that is,
this user will have CREATEROLE privilege.
- See 'role-creation' /> for more details about what
+ See "role-creation"/> for more details about what
capabilities are conferred by this privilege.
- 'pgbench-metacommand-gset'>
+ "pgbench-metacommand-gset">
\gset [prefix]
\aset [prefix]
- 'pgbench-metacommand-set'>
+ "pgbench-metacommand-set">
\set varname expression
- 'pgbench-metacommand-pipeline'>
+ "pgbench-metacommand-pipeline">
\startpipeline
\endpipeline
-
'role-creation'>role creationroleprivilege to create
+
"role-creation">role creationroleprivilege to create
A role must be explicitly given permission to create more roles