PostgreSQL
52.64. System Views
In addition to the system catalogs, PostgreSQL provides a number of built-in views. Some system views provide convenient access to some commonly used queries on the system catalogs. Other views provide access to internal server state.
The information schema (Chapter 37) provides an alternative set of views which overlap the functionality of the system views. Since the information schema is SQL-standard whereas the views described here are PostgreSQL-specific, it’s usually better to use the information schema if it provides all the information you need.
Table 52.65 lists the system views described here. More detailed documentation of each view follows below. There are some additional views that provide access to the results of the statistics collector; they are described in Table 28.2.
Except where noted, all the views described here are read-only.
Table 52.65. System Views
View Name | Purpose |
---|---|
available extensions |
|
available versions of extensions |
|
backend memory contexts |
|
compile-time configuration parameters |
|
open cursors |
|
summary of configuration file contents |
|
groups of database users |
|
summary of client authentication configuration file contents |
|
indexes |
|
locks currently held or awaited |
|
materialized views |
|
policies |
|
prepared statements |
|
prepared transactions |
|
publications and their associated tables |
|
information about replication origins, including replication progress |
|
replication slot information |
|
database roles |
|
rules |
|
security labels |
|
sequences |
|
parameter settings |
|
database users |
|
shared memory allocations |
|
planner statistics |
|
extended planner statistics |
|
extended planner statistics for expressions |
|
tables |
|
time zone abbreviations |
|
time zone names |
|
database users |
|
user mappings |
|
views |
+
Prev | Up | Next |
---|---|---|
52.63. |
52.65. |
Submit correction
If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.
Copyright © 1996-2023 The PostgreSQL Global Development Group