System Catalogs / Version comparison
What changed?
System Catalogs · PostgreSQL 8.0 → 8.1
Historical documentation for a PostgreSQL version that is no longer supported.
7 added · 0 removed · 15 changed · 10 reworded · 0 with columns not listed. These are changes between the pinned reference snapshots. “Changed” means columns, their types, their order or a measured attribute such as NOT NULL; “reworded” means only the manual's descriptions.
changedpg_aggregate
8.0 → 8.1 + aggsortop oid
changedpg_am
8.0 → 8.1 + amoptionalkey boolean + amgetmulti regproc - amowner integer ~ column order changed
addedpg_auth_members
--- 8.0 +++ 8.1 @@ -0,0 +1,4 @@ +roleid oid +member oid +grantor oid +admin_option boolean
addedpg_authid
--- 8.0 +++ 8.1 @@ -0,0 +1,11 @@ +rolname name +rolsuper boolean +rolinherit boolean +rolcreaterole boolean +rolcreatedb boolean +rolcatupdate boolean +rolcanlogin boolean +rolconnlimit integer +rolpassword text +rolvaliduntil timestamp with time zone +rolconfig text[]
addedpg_autovacuum
--- 8.0 +++ 8.1 @@ -0,0 +1,8 @@ +vacrelid oid +enabled boolean +vac_base_thresh integer +vac_scale_factor real +anl_base_thresh integer +anl_scale_factor real +vac_cost_delay integer +vac_cost_limit integer
changedpg_class
8.0 → 8.1 ~ relowner integer → oid
changedpg_conversion
8.0 → 8.1 ~ conowner integer → oid
changedpg_database
8.0 → 8.1 + datconnlimit integer ~ datdba integer → oid
rewordedpg_depend
--- 8.0 +++ 8.1 @@ -1,4 +1,4 @@ -(relation) The catalog pg_depend records the dependency relationships between database objects. This information allows DROP commands to find which other objects must be dropped by DROP CASCADE or prevent dropping in the DROP RESTRICT case. +(relation) The catalog pg_depend records the dependency relationships between database objects. This information allows DROP commands to find which other objects must be dropped by DROP CASCADE or prevent dropping in the DROP RESTRICT case. See also pg_shdepend, which performs a similar function for dependencies involving objects that are shared across a database cluster. classid: The OID of the system catalog the dependent object is in objid: The OID of the specific dependent object objsubid: For a table column, this is the column number (the objid and classid refer to the table itself). For all other object types, this column is zero.
changedpg_group
8.0 → 8.1 ~ grolist integer[] → oid[] ~ grosysid integer → oid
changedpg_index
8.0 → 8.1 ~ column order changed
rewordedpg_language
--- 8.0 +++ 8.1 @@ -1,7 +1,7 @@ -(relation) The catalog pg_language registers languages in which you can write functions or stored procedures. See CREATE LANGUAGE and Chapter 34 for more information about language handlers. +(relation) The catalog pg_language registers languages in which you can write functions or stored procedures. See CREATE LANGUAGE and Chapter 35 for more information about language handlers. lanname: Name of the language lanispl: This is false for internal languages (such as SQL) and true for user-defined languages. Currently, pg_dump still uses this to determine which languages need to be dumped, but this may be replaced by a different mechanism sometime. -lanpltrusted: This is a trusted language. If this is an internal language (lanispl is false) then this column is meaningless. +lanpltrusted: True if this is a trusted language, which means that it is believed not to grant access to anything outside the normal SQL execution environment. Only superusers may create functions in untrusted languages. lanplcallfoid: For noninternal languages this references the language handler, which is a special function that is responsible for executing all functions that are written in the particular language. lanvalidator: This references a language validator function that is responsible for checking the syntax and validity of new functions when they are created. Zero if no validator is provided. lanacl: Access privileges; see GRANT and REVOKE for details.
changedpg_locks
8.0 → 8.1 + locktype text + page integer + tuple smallint + transactionid xid + classid oid + objid oid + objsubid smallint ~ column order changed
changedpg_namespace
8.0 → 8.1 ~ nspowner integer → oid
changedpg_opclass
8.0 → 8.1 ~ opcowner integer → oid
changedpg_operator
8.0 → 8.1 ~ oprowner integer → oid
addedpg_pltemplate
--- 8.0 +++ 8.1 @@ -0,0 +1,6 @@ +tmplname name +tmpltrusted boolean +tmplhandler text +tmplvalidator text +tmpllibrary text +tmplacl aclitem[]
addedpg_prepared_xacts
--- 8.0 +++ 8.1 @@ -0,0 +1,5 @@ +transaction xid +gid text +prepared timestamp with time zone +owner name +database name
changedpg_proc
8.0 → 8.1 + proallargtypes oid[] + proargmodes "char"[] ~ proowner integer → oid
addedpg_roles
--- 8.0 +++ 8.1 @@ -0,0 +1,11 @@ +rolname name +rolsuper boolean +rolinherit boolean +rolcreaterole boolean +rolcreatedb boolean +rolcatupdate boolean +rolcanlogin boolean +rolconnlimit integer +rolpassword text +rolvaliduntil timestamp with time zone +rolconfig text[]
changedpg_shadow
8.0 → 8.1 ~ usesysid integer → oid
addedpg_shdepend
--- 8.0 +++ 8.1 @@ -0,0 +1,6 @@ +dbid oid +classid oid +objid oid +refclassid oid +refobjid oid +deptype "char"
rewordedpg_stat_activity
--- 8.0 +++ 8.1 @@ -1 +1 @@ -(relation) One row per server process, showing process ID, database, user, current query, and the time at which the current query began execution. The columns that report data on the current query are only available if the parameter stats_command_string has been turned on. Furthermore, these columns read as null unless the user examining the view is a superuser or the same as the user owning the process being reported on. (Note that because of the collector's reporting delay, current query will only be up-to-date for long-running queries.) +(relation) One row per server process, showing database OID, database name, process ID, user OID, user name, current query, time at which the current query began execution, time at which the process was started, and client's address and port number. The columns that report data on the current query are only available if the parameter stats_command_string has been turned on. Furthermore, these columns read as null unless the user examining the view is a superuser or the same as the user owning the process being reported on. (Note that because of the collector's reporting delay, the current query will only be up-to-date for long-running queries.)
rewordedpg_stat_all_indexes
--- 8.0 +++ 8.1 @@ -1 +1 @@ -(relation) For each index in the current database, the total number of index scans that have used that index, the number of index rows read, and the number of successfully fetched heap rows. (This may be less when there are index entries pointing to expired heap rows.) +(relation) For each index in the current database, the table and index OID, schema, table and index name, number of index scans initiated on that index, number of index entries returned by index scans, and number of live table rows fetched by simple index scans using that index.
rewordedpg_stat_all_tables
--- 8.0 +++ 8.1 @@ -1 +1 @@ -(relation) For each table in the current database, total numbers of sequential and index scans, total numbers of rows returned by each type of scan, and totals of row insertions, updates, and deletions. +(relation) For each table in the current database (including TOAST tables), the table OID, schema and table name, number of sequential scans initiated, number of live rows fetched by sequential scans, number of index scans initiated (over all indexes belonging to the table), number of live rows fetched by index scans, and numbers of row insertions, updates, and deletions.
rewordedpg_stat_database
--- 8.0 +++ 8.1 @@ -1 +1 @@ -(relation) One row per database, showing the number of active backend server processes, total transactions committed and total rolled back in that database, total disk blocks read, and total number of buffer hits (i.e., block read requests avoided by finding the block already in buffer cache). +(relation) One row per database, showing database OID, database name, number of active server processes connected to that database, number of transactions committed and rolled back in that database, total disk blocks read, and total buffer hits (i.e., block read requests avoided by finding the block already in buffer cache).
rewordedpg_statio_all_indexes
--- 8.0 +++ 8.1 @@ -1 +1 @@ -(relation) For each index in the current database, the numbers of disk blocks read and buffer hits in that index. +(relation) For each index in the current database, the table and index OID, schema, table and index name, numbers of disk blocks read and buffer hits in that index.
rewordedpg_statio_all_sequences
--- 8.0 +++ 8.1 @@ -1 +1 @@ -(relation) For each sequence object in the current database, the numbers of disk blocks read and buffer hits in that sequence. +(relation) For each sequence object in the current database, the sequence OID, schema and sequence name, numbers of disk blocks read and buffer hits in that sequence.
rewordedpg_statio_all_tables
--- 8.0 +++ 8.1 @@ -1 +1 @@ -(relation) For each table in the current database, the total number of disk blocks read from that table, the number of buffer hits, the numbers of disk blocks read and buffer hits in all the indexes of that table, the numbers of disk blocks read and buffer hits from the table's auxiliary TOAST table (if any), and the numbers of disk blocks read and buffer hits for the TOAST table's index. +(relation) For each table in the current database (including TOAST tables), the table OID, schema and table name, number of disk blocks read from that table, number of buffer hits, numbers of disk blocks read and buffer hits in all indexes of that table, numbers of disk blocks read and buffer hits from that table's auxiliary TOAST table (if any), and numbers of disk blocks read and buffer hits for the TOAST table's index.
changedpg_tablespace
8.0 → 8.1 ~ spcowner integer → oid
rewordedpg_trigger
--- 8.0 +++ 8.1 @@ -3,7 +3,7 @@ tgname: Trigger name (must be unique among triggers of same table) tgfoid: The function to be called tgtype: Bit mask identifying trigger conditions -tgenabled: True if trigger is enabled (not presently checked everywhere it should be, so disabling a trigger by setting this false does not work reliably) +tgenabled: True if trigger is enabled tgisconstraint: True if trigger implements a referential integrity constraint tgconstrname: Referential integrity constraint name tgconstrrelid: The table referenced by an referential integrity constraint
changedpg_type
8.0 → 8.1 ~ typowner integer → oid