aggregate functions
FOLLOW THE EVOLUTION
PostgreSQL 9.0 Coverage Baseline
Start from a single upgrade and see how catalogs, columns, and types changed.
Compare any two versions, or walk forward through the release history.
This comparison includes the PostgreSQL 19 beta 3 snapshot; the result does not represent the final released structure.
relation access methods
access method operators
access method support functions
column default values
table columns (“attributes”)
authorization identifier membership relationships
authorization identifiers (roles)
casts (data type conversions)
tables, indexes, sequences, views (“relations”)
check constraints, unique constraints, primary key constraints, foreign key constraints
encoding conversion information
The pg_cursors view lists the cursors that are currently available. Cursors can be defined in several ways:
databases within this database cluster
per-role and per-database settings
default privileges for object types
dependencies between database objects
descriptions or comments on database objects
enum label and value definitions
foreign-data wrapper definitions
foreign server definitions
The view pg_group exists for backwards compatibility: it emulates a catalog that existed in PostgreSQL before version 8.1. It shows the names and members of all roles that are marked as not rolcanlogin, which is an approximation to the set of roles that are being used as groups.
additional index information
The view pg_indexes provides access to useful information about each index in the database.
table inheritance hierarchy
languages for writing functions
data pages for large objects
metadata for large objects
The view pg_locks provides access to information about the locks held by active processes within the database server. See Chapter 13 for more discussion of locking.
schemas
access method operator classes
operators
access method operator families
template data for procedural languages
The pg_prepared_statements view displays all the prepared statements that are available in the current session. See PREPARE for more information about prepared statements.
The view pg_prepared_xacts displays information about transactions that are currently prepared for two-phase commit (see PREPARE TRANSACTION for details).
functions and procedures
query rewrite rules
The view pg_roles provides access to information about database roles. This is simply a publicly readable view of pg_authid that blanks out the password field.
The view pg_rules provides access to useful information about query rewrite rules.
The view pg_settings provides access to run-time parameters of the server. It is essentially an alternative interface to the SHOW and SET commands. It also provides access to some facts about each parameter that are not directly available from SHOW, such as minimum and maximum values.
The view pg_shadow exists for backwards compatibility: it emulates a catalog that existed in PostgreSQL before version 8.1. It shows properties of all roles that are marked as rolcanlogin in pg_authid.
dependencies on shared objects
comments on shared objects
One row per server process, showing information related to the current activity of that process, such as state and current query. See pg_stat_activity for details.
One row for each index in the current database, showing statistics about accesses to that specific index. See pg_stat_all_indexes for details.
One row for each table in the current database, showing statistics about accesses to that specific table. See pg_stat_all_tables for details.
One row only, showing statistics about the background writer process's activity. See pg_stat_bgwriter for details.
One row per database, showing database-wide statistics. See pg_stat_database for details.
Same as pg_stat_all_indexes, except that only indexes on system tables are shown.
Same as pg_stat_all_tables, except that only system tables are shown.
One row for each tracked function, showing statistics about executions of that function. See pg_stat_user_functions for details.
Same as pg_stat_all_indexes, except that only indexes on user tables are shown.
Same as pg_stat_all_tables, except that only user tables are shown.
One row for each index in the current database, showing statistics about I/O on that specific index. See pg_statio_all_indexes for details.
One row for each sequence in the current database, showing statistics about I/O on that specific sequence. See pg_statio_all_sequences for details.
One row for each table in the current database, showing statistics about I/O on that specific table. See pg_statio_all_tables for details.
Same as pg_statio_all_indexes, except that only indexes on system tables are shown.
Same as pg_statio_all_sequences, except that only system sequences are shown. (Presently, no system sequences are defined, so this view is always empty.)
Same as pg_statio_all_tables, except that only system tables are shown.
Same as pg_statio_all_indexes, except that only indexes on user tables are shown.
Same as pg_statio_all_sequences, except that only user sequences are shown.
Same as pg_statio_all_tables, except that only user tables are shown.
planner statistics
The view pg_stats provides access to the information stored in the pg_statistic catalog. This view allows access only to rows of pg_statistic that correspond to tables the user has permission to read, and therefore it is safe to allow public read access to this view.
The view pg_tables provides access to useful information about each table in the database.
tablespaces within this database cluster
The view pg_timezone_abbrevs provides a list of time zone abbreviations that are currently recognized by the datetime input routines. The contents of this view change when the TimeZone or timezone_abbreviations run-time parameters are modified.
The view pg_timezone_names provides a list of time zone names that are recognized by SET TIMEZONE, along with their associated abbreviations, UTC offsets, and daylight-savings status. (Technically, PostgreSQL does not use UTC because leap seconds are not handled.) Unlike the abbreviations shown in pg_timezone_abbrevs, many of these names imply a set of daylight-savings transition date rules. Therefore, the associated information changes across local DST boundaries. The displayed information is computed based on the current value of CURRENT_TIMESTAMP.
triggers
text search configurations
text search configurations' token mappings
text search dictionaries
text search parsers
text search templates
data types
The view pg_user provides access to information about database users. This is simply a publicly readable view of pg_shadow that blanks out the password field.
mappings of users to foreign servers
The view pg_user_mappings provides access to information about user mappings. This is essentially a publicly readable view of pg_user_mapping that leaves out the options field if the user has no rights to use it.
The view pg_views provides access to useful information about each view in the database.