What changed?

--- 8.1
+++ 8.2
@@ -4,4 +4,4 @@
 aggfinalfn: Final function (zero if none)
 aggsortop: Associated sort operator (zero if none)
 aggtranstype: Data type of the aggregate function's internal transition (state) data
-agginitval: The initial value of the transition state. This is a text field containing the initial value in its external string representation. If this field is null, the transition state value starts out null.
+agginitval: The initial value of the transition state. This is a text field containing the initial value in its external string representation. If this field is NULL, the transition state value starts out NULL

8.1 → 8.2
+ amstorage  boolean
+ amclusterable  boolean
+ amoptions  regproc
- amconcurrent  boolean

--- 8.1
+++ 8.2
@@ -2,17 +2,17 @@
 attrelid: The table this column belongs to
 attname: The column name
 atttypid: The data type of this column
-attstattarget: attstattarget controls the level of detail of statistics accumulated for this column by ANALYZE. A zero value indicates that no statistics should be collected. A negative value says to use the system default statistics target. The exact meaning of positive values is data type-dependent. For scalar data types, attstattarget is both the target number of "most common values" to collect, and the target number of histogram bins to create.
+attstattarget: attstattarget controls the level of detail of statistics accumulated for this column by ANALYZE. A zero value indicates that no statistics should be collected. A negative value says to use the system default statistics target. The exact meaning of positive values is data type-dependent. For scalar data types, attstattarget is both the target number of "most common values" to collect, and the target number of histogram bins to create
 attlen: A copy of pg_type.typlen of this column's type
-attnum: The number of the column. Ordinary columns are numbered from 1 up. System columns, such as oid, have (arbitrary) negative numbers.
-attndims: Number of dimensions, if the column is an array type; otherwise 0. (Presently, the number of dimensions of an array is not enforced, so any nonzero value effectively means "it's an array".)
-attcacheoff: Always -1 in storage, but when loaded into a row descriptor in memory this may be updated to cache the offset of the attribute within the row.
-atttypmod: atttypmod records type-specific data supplied at table creation time (for example, the maximum length of a varchar column). It is passed to type-specific input functions and length coercion functions. The value will generally be -1 for types that do not need atttypmod.
+attnum: The number of the column. Ordinary columns are numbered from 1 up. System columns, such as oid, have (arbitrary) negative numbers
+attndims: Number of dimensions, if the column is an array type; otherwise 0. (Presently, the number of dimensions of an array is not enforced, so any nonzero value effectively means "it's an array")
+attcacheoff: Always -1 in storage, but when loaded into a row descriptor in memory this may be updated to cache the offset of the attribute within the row
+atttypmod: atttypmod records type-specific data supplied at table creation time (for example, the maximum length of a varchar column). It is passed to type-specific input functions and length coercion functions. The value will generally be -1 for types that do not need atttypmod
 attbyval: A copy of pg_type.typbyval of this column's type
-attstorage: Normally a copy of pg_type.typstorage of this column's type. For TOAST-able data types, this can be altered after column creation to control storage policy.
+attstorage: Normally a copy of pg_type.typstorage of this column's type. For TOAST-able data types, this can be altered after column creation to control storage policy
 attalign: A copy of pg_type.typalign of this column's type
-attnotnull: This represents a not-null constraint. It is possible to change this column to enable or disable the constraint.
-atthasdef: This column has a default value, in which case there will be a corresponding entry in the pg_attrdef catalog that actually defines the value.
-attisdropped: This column has been dropped and is no longer valid. A dropped column is still physically present in the table, but is ignored by the parser and so cannot be accessed via SQL.
-attislocal: This column is defined locally in the relation. Note that a column may be locally defined and inherited simultaneously.
-attinhcount: The number of direct ancestors this column has. A column with a nonzero number of ancestors cannot be dropped nor renamed.
+attnotnull: This represents a not-null constraint. It is possible to change this column to enable or disable the constraint
+atthasdef: This column has a default value, in which case there will be a corresponding entry in the pg_attrdef catalog that actually defines the value
+attisdropped: This column has been dropped and is no longer valid. A dropped column is still physically present in the table, but is ignored by the parser and so cannot be accessed via SQL
+attislocal: This column is defined locally in the relation. Note that a column may be locally defined and inherited simultaneously
+attinhcount: The number of direct ancestors this column has. A column with a nonzero number of ancestors cannot be dropped nor renamed

--- 8.1
+++ 8.2
@@ -4,9 +4,9 @@
 rolinherit: Role automatically inherits privileges of roles it is a member of
 rolcreaterole: Role may create more roles
 rolcreatedb: Role may create databases
-rolcatupdate: Role may update system catalogs directly. (Even a superuser may not do this unless this column is true.)
-rolcanlogin: Role may log in, that is, this role can be given as the initial session authorization identifier.
-rolconnlimit: For roles that can log in, this sets maximum number of concurrent connections this role can make. -1 means no limit.
+rolcatupdate: Role may update system catalogs directly. (Even a superuser may not do this unless this column is true)
+rolcanlogin: Role may log in. That is, this role can be given as the initial session authorization identifier
+rolconnlimit: For roles that can log in, this sets maximum number of concurrent connections this role can make. -1 means no limit
 rolpassword: Password (possibly encrypted); NULL if none
 rolvaliduntil: Password expiry time (only used for password authentication); NULL if no expiration
 rolconfig: Session defaults for run-time configuration variables

8.1 → 8.2
+ freeze_min_age  integer
+ freeze_max_age  integer

--- 8.1
+++ 8.2
@@ -1,5 +1,5 @@
 (relation) The catalog pg_cast stores data type conversion paths, both built-in paths and those defined with CREATE CAST.
 castsource: OID of the source data type
 casttarget: OID of the target data type
-castfunc: The OID of the function to use to perform this cast. Zero is stored if the data types are binary compatible (that is, no run-time operation is needed to perform the cast).
-castcontext: Indicates what contexts the cast may be invoked in. e means only as an explicit cast (using CAST or :: syntax). a means implicitly in assignment to a target column, as well as explicitly. i means implicitly in expressions, as well as the other cases.
+castfunc: The OID of the function to use to perform this cast. Zero is stored if the data types are binary compatible (that is, no run-time operation is needed to perform the cast)
+castcontext: Indicates what contexts the cast may be invoked in. e means only as an explicit cast (using CAST or :: syntax). a means implicitly in assignment to a target column, as well as explicitly. i means implicitly in expressions, as well as the other cases

8.1 → 8.2
+ relfrozenxid  xid
+ reloptions  text[]

--- 8.1
+++ 8.2
@@ -0,0 +1,6 @@
+name  text
+statement  text
+is_holdable  boolean
+is_binary  boolean
+is_scrollable  boolean
+creation_time  timestamp with time zone

8.1 → 8.2
- datvacuumxid  xid

--- 8.1
+++ 8.2
@@ -1,8 +1,8 @@
 (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.
+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
 refclassid: The OID of the system catalog the referenced object is in
 refobjid: The OID of the specific referenced object
-refobjsubid: For a table column, this is the column number (the refobjid and refclassid refer to the table itself). For all other object types, this column is zero.
-deptype: A code defining the specific semantics of this dependency relationship; see text.
+refobjsubid: For a table column, this is the column number (the refobjid and refclassid refer to the table itself). For all other object types, this column is zero
+deptype: A code defining the specific semantics of this dependency relationship; see text

--- 8.1
+++ 8.2
@@ -1,5 +1,5 @@
-(relation) The catalog pg_description stores optional descriptions (comments) for each database object. Descriptions can be manipulated with the COMMENT command and viewed with psql's \d commands. Descriptions of many built-in system objects are provided in the initial contents of pg_description.
+(relation) The catalog pg_description stores optional descriptions (comments) for each database object. Descriptions can be manipulated with the COMMENT command and viewed with psql's \d commands. Descriptions of many built-in system objects are provided in the initial contents of pg_description. See also pg_shdescription, which performs a similar function for descriptions involving objects that are shared across a database cluster.
 objoid: The OID of the object this description pertains to
 classoid: The OID of the system catalog this object appears in
-objsubid: For a comment on a table column, this is the column number (the objoid and classoid refer to the table itself). For all other object types, this column is zero.
-description: Arbitrary text that serves as the description of this object.
+objsubid: For a comment on a table column, this is the column number (the objoid and classoid refer to the table itself). For all other object types, this column is zero
+description: Arbitrary text that serves as the description of this object

8.1 → 8.2
+ indisvalid  boolean

--- 8.1
+++ 8.2
@@ -1,6 +1,6 @@
 (relation) The view pg_indexes provides access to useful information about each index in the database.
-schemaname: name of schema containing table and index
-tablename: name of table the index is for
-indexname: name of index
-tablespace: name of tablespace containing index (NULL if default for database)
-indexdef: index definition (a reconstructed creation command)
+schemaname: Name of schema containing table and index
+tablename: Name of table the index is for
+indexname: Name of index
+tablespace: Name of tablespace containing index (NULL if default for database)
+indexdef: Index definition (a reconstructed CREATE INDEX command)

--- 8.1
+++ 8.2
@@ -1,4 +1,4 @@
 (relation) The catalog pg_inherits records information about table inheritance hierarchies. There is one entry for each direct child table in the database. (Indirect inheritance can be determined by following chains of entries.)
-inhrelid: The OID of the child table.
-inhparent: The OID of the parent table.
-inhseqno: If there is more than one direct parent for a child table (multiple inheritance), this number tells the order in which the inherited columns are to be arranged. The count starts at 1.
+inhrelid: The OID of the child table
+inhparent: The OID of the parent table
+inhseqno: If there is more than one direct parent for a child table (multiple inheritance), this number tells the order in which the inherited columns are to be arranged. The count starts at 1

--- 8.1
+++ 8.2
@@ -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 35 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 36 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: 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.
+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 in the future
+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

--- 8.1
+++ 8.2
@@ -1,4 +1,4 @@
 (relation) The catalog pg_largeobject holds the data making up "large objects". A large object is identified by an OID assigned when it is created. Each large object is broken into segments or "pages" small enough to be conveniently stored as rows in pg_largeobject. The amount of data per page is defined to be LOBLKSIZE (which is currently BLCKSZ/4, or typically 2 kB).
 loid: Identifier of the large object that includes this page
 pageno: Page number of this page within its large object (counting from zero)
-data: Actual data stored in the large object. This will never be more than LOBLKSIZE bytes and may be less.
+data: Actual data stored in the large object. This will never be more than LOBLKSIZE bytes and may be less

--- 8.1
+++ 8.2
@@ -1,4 +1,4 @@
 (relation) The catalog pg_listener supports the LISTEN and NOTIFY commands. A listener creates an entry in pg_listener for each notification name it is listening for. A notifier scans pg_listener and updates each matching entry to show that a notification has occurred. The notifier also sends a signal (using the PID recorded in the table) to awaken the listener from sleep.
 relname: Notify condition name. (The name need not match any actual relation in the database; the name relname is historical.)
-listenerpid: PID of the server process that created this entry.
-notification: Zero if no event is pending for this listener. If an event is pending, the PID of the server process that sent the notification.
+listenerpid: PID of the server process that created this entry
+notification: Zero if no event is pending for this listener. If an event is pending, the PID of the server process that sent the notification

--- 8.1
+++ 8.2
@@ -1,14 +1,14 @@
 (relation) The view pg_locks provides access to information about the locks held by open transactions within the database server. See Chapter 12 for more discussion of locking. pg_locks contains one row per active lockable object, requested lock mode, and relevant transaction. Thus, the same lockable object may appear many times, if multiple transactions are holding or waiting for locks on it. However, an object that currently has no locks on it will not appear at all. There are several distinct types of lockable objects: whole relations (e.g., tables), individual pages of relations, individual tuples of relations, transaction IDs, and general database objects (identified by class OID and object OID, in the same way as in pg_description or pg_depend). Also, the right to extend a relation is represented as a separate lockable object.
-locktype: type of the lockable object: relation, extend, page, tuple, transactionid, object, or userlock
+locktype: type of the lockable object: relation, extend, page, tuple, transactionid, object, userlock, or advisory
 database: OID of the database in which the object exists, or zero if the object is a shared object, or NULL if the object is a transaction ID
 relation: OID of the relation, or NULL if the object is not a relation or part of a relation
-page: page number within the relation, or NULL if the object is not a tuple or relation page
-tuple: tuple number within the page, or NULL if the object is not a tuple
+page: Page number within the relation, or NULL if the object is not a tuple or relation page
+tuple: Tuple number within the page, or NULL if the object is not a tuple
 transactionid: ID of a transaction, or NULL if the object is not a transaction ID
 classid: OID of the system catalog containing the object, or NULL if the object is not a general database object
 objid: OID of the object within its system catalog, or NULL if the object is not a general database object
 objsubid: For a table column, this is the column number (the classid and objid refer to the table itself). For all other object types, this column is zero. NULL if the object is not a general database object
-transaction: ID of the transaction that is holding or awaiting this lock.
-pid: Process ID of the server process holding or awaiting this lock. Null if the lock is held by a prepared transaction.
-mode: name of the lock mode held or desired by this process (see Section 12.3.1)
-granted: true if lock is held, false if lock is awaited
+transaction: ID of the transaction that is holding or awaiting this lock
+pid: Process ID of the server process holding or awaiting this lock. NULL if the lock is held by a prepared transaction
+mode: Name of the lock mode held or desired by this process (see Section 12.3.1)
+granted: True if lock is held, false if lock is awaited

--- 8.1
+++ 8.2
@@ -1,4 +1,4 @@
 (relation) The catalog pg_namespace stores namespaces. A namespace is the structure underlying SQL schemas: each namespace can have a separate collection of relations, types, etc. without name conflicts.
 nspname: Name of the namespace
 nspowner: Owner of the namespace
-nspacl: Access privileges; see GRANT and REVOKE for details.
+nspacl: Access privileges; see GRANT and REVOKE for details

--- 8.1
+++ 8.2
@@ -1,4 +1,4 @@
-(relation) The catalog pg_opclass defines index access method operator classes. Each operator class defines semantics for index columns of a particular data type and a particular index access method. Note that there can be multiple operator classes for a given data type/access method combination, thus supporting multiple behaviors. Operator classes are described at length in Section 32.14.
+(relation) The catalog pg_opclass defines index access method operator classes. Each operator class defines semantics for index columns of a particular data type and a particular index access method. Note that there can be multiple operator classes for a given data type/access method combination, thus supporting multiple behaviors. Operator classes are described at length in Section 33.14.
 opcamid: Index access method operator class is for
 opcname: Name of this operator class
 opcnamespace: Namespace of this operator class

--- 8.1
+++ 8.2
@@ -1,4 +1,4 @@
-(relation) The catalog pg_operator stores information about operators. See CREATE OPERATOR and Section 32.12 for more information.
+(relation) The catalog pg_operator stores information about operators. See CREATE OPERATOR and Section 33.12 for more information.
 oprname: Name of the operator
 oprnamespace: The OID of the namespace that contains this operator
 oprowner: Owner of the operator

--- 8.1
+++ 8.2
@@ -0,0 +1,5 @@
+name  text
+statement  text
+prepare_time  timestamp with time zone
+parameter_types  regtype[]
+from_sql  boolean

--- 8.1
+++ 8.2
@@ -1,19 +1,19 @@
-(relation) The catalog pg_proc stores information about functions (or procedures). See CREATE FUNCTION and Section 32.3 for more information. The table contains data for aggregate functions as well as plain functions. If proisagg is true, there should be a matching row in pg_aggregate.
+(relation) The catalog pg_proc stores information about functions (or procedures). See CREATE FUNCTION and Section 33.3 for more information. The table contains data for aggregate functions as well as plain functions. If proisagg is true, there should be a matching row in pg_aggregate.
 proname: Name of the function
 pronamespace: The OID of the namespace that contains this function
 proowner: Owner of the function
 prolang: Implementation language or call interface of this function
 proisagg: Function is an aggregate function
 prosecdef: Function is a security definer (i.e., a "setuid" function)
-proisstrict: Function returns null if any call argument is null. In that case the function won't actually be called at all. Functions that are not "strict" must be prepared to handle null inputs.
+proisstrict: Function returns null if any call argument is null. In that case the function won't actually be called at all. Functions that are not "strict" must be prepared to handle null inputs
 proretset: Function returns a set (i.e., multiple values of the specified data type)
 provolatile: provolatile tells whether the function's result depends only on its input arguments, or is affected by outside factors. It is i for "immutable" functions, which always deliver the same result for the same inputs. It is s for "stable" functions, whose results (for fixed inputs) do not change within a scan. It is v for "volatile" functions, whose results may change at any time. (Use v also for functions with side-effects, so that calls to them cannot get optimized away.)
 pronargs: Number of arguments
 prorettype: Data type of the return value
-proargtypes: An array with the data types of the function arguments. This includes only input arguments (including INOUT arguments), and thus represents the call signature of the function.
-proallargtypes: An array with the data types of the function arguments. This includes all arguments (including OUT and INOUT arguments); however, if all the arguments are IN arguments, this field will be null. Note that subscripting is 1-based, whereas for historical reasons proargtypes is subscripted from 0.
-proargmodes: An array with the modes of the function arguments, encoded as i for IN arguments, o for OUT arguments, b for INOUT arguments. If all the arguments are IN arguments, this field will be null. Note that subscripts correspond to positions of proallargtypes not proargtypes.
-proargnames: An array with the names of the function arguments. Arguments without a name are set to empty strings in the array. If none of the arguments have a name, this field will be null. Note that subscripts correspond to positions of proallargtypes not proargtypes.
-prosrc: This tells the function handler how to invoke the function. It might be the actual source code of the function for interpreted languages, a link symbol, a file name, or just about anything else, depending on the implementation language/call convention.
-probin: Additional information about how to invoke the function. Again, the interpretation is language-specific.
-proacl: Access privileges; see GRANT and REVOKE for details.
+proargtypes: An array with the data types of the function arguments. This includes only input arguments (including INOUT arguments), and thus represents the call signature of the function
+proallargtypes: An array with the data types of the function arguments. This includes all arguments (including OUT and INOUT arguments); however, if all the arguments are IN arguments, this field will be null. Note that subscripting is 1-based, whereas for historical reasons proargtypes is subscripted from 0
+proargmodes: An array with the modes of the function arguments, encoded as i for IN arguments, o for OUT arguments, b for INOUT arguments. If all the arguments are IN arguments, this field will be null. Note that subscripts correspond to positions of proallargtypes not proargtypes
+proargnames: An array with the names of the function arguments. Arguments without a name are set to empty strings in the array. If none of the arguments have a name, this field will be null. Note that subscripts correspond to positions of proallargtypes not proargtypes
+prosrc: This tells the function handler how to invoke the function. It might be the actual source code of the function for interpreted languages, a link symbol, a file name, or just about anything else, depending on the implementation language/call convention
+probin: Additional information about how to invoke the function. Again, the interpretation is language-specific
+proacl: Access privileges; see GRANT and REVOKE for details

--- 8.1
+++ 8.2
@@ -5,8 +5,8 @@
 rolcreaterole: Role may create more roles
 rolcreatedb: Role may create databases
 rolcatupdate: Role may update system catalogs directly. (Even a superuser may not do this unless this column is true.)
-rolcanlogin: Role may log in, that is, this role can be given as the initial session authorization identifier.
-rolconnlimit: For roles that can log in, this sets maximum number of concurrent connections this role can make. -1 means no limit.
+rolcanlogin: Role may log in. That is, this role can be given as the initial session authorization identifier
+rolconnlimit: For roles that can log in, this sets maximum number of concurrent connections this role can make. -1 means no limit
 rolpassword: Not the password (always reads as ********)
 rolvaliduntil: Password expiry time (only used for password authentication); NULL if no expiration
 rolconfig: Session defaults for run-time configuration variables

--- 8.1
+++ 8.2
@@ -1,5 +1,5 @@
 (relation) The view pg_rules provides access to useful information about query rewrite rules.
-schemaname: name of schema containing table
-tablename: name of table the rule is for
-rulename: name of rule
-definition: rule definition (a reconstructed creation command)
+schemaname: Name of schema containing table
+tablename: Name of table the rule is for
+rulename: Name of rule
+definition: Rule definition (a reconstructed creation command)

8.1 → 8.2
+ unit  text

--- 8.1
+++ 8.2
@@ -4,4 +4,4 @@
 objid: The OID of the specific dependent object
 refclassid: The OID of the system catalog the referenced object is in (must be a shared catalog)
 refobjid: The OID of the specific referenced object
-deptype: A code defining the specific semantics of this dependency relationship; see text.
+deptype: A code defining the specific semantics of this dependency relationship; see text

--- 8.1
+++ 8.2
@@ -0,0 +1,3 @@
+objoid  oid
+classoid  oid
+description  text

--- 8.1
+++ 8.2
@@ -1 +1 @@
-(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.)
+(relation) One row per server process, showing database OID, database name, process ID, user OID, user name, current query, query's waiting status, 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 available unless the parameter stats_command_string has been turned off. Furthermore, these columns are only visible if the user examining the view is a superuser or the same as the user owning the process being reported on.

--- 8.1
+++ 8.2
@@ -1 +1 @@
-(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.
+(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, numbers of row insertions, updates, and deletions, the last time the table was vacuumed manually, the last time it was vacuumed by the autovacuum daemon, the last time it was analyzed manually, and the last time it was analyzed by the autovacuum daemon.

--- 8.1
+++ 8.2
@@ -3,8 +3,8 @@
 staattnum: The number of the described column
 stanullfrac: The fraction of the column's entries that are null
 stawidth: The average stored width, in bytes, of nonnull entries
-stadistinct: The number of distinct nonnull data values in the column. A value greater than zero is the actual number of distinct values. A value less than zero is the negative of a fraction of the number of rows in the table (for example, a column in which values appear about twice on the average could be represented by stadistinct = -0.5). A zero value means the number of distinct values is unknown.
-stakindN: A code number indicating the kind of statistics stored in the Nth "slot" of the pg_statistic row.
-staopN: An operator used to derive the statistics stored in the Nth "slot". For example, a histogram slot would show the < operator that defines the sort order of the data.
-stanumbersN: Numerical statistics of the appropriate kind for the Nth "slot", or null if the slot kind does not involve numerical values.
-stavaluesN: Column data values of the appropriate kind for the Nth "slot", or null if the slot kind does not store any data values. Each array's element values are actually of the specific column's data type, so there is no way to define these columns' type more specifically than anyarray.
+stadistinct: The number of distinct nonnull data values in the column. A value greater than zero is the actual number of distinct values. A value less than zero is the negative of a fraction of the number of rows in the table (for example, a column in which values appear about twice on the average could be represented by stadistinct = -0.5). A zero value means the number of distinct values is unknown
+stakindN: A code number indicating the kind of statistics stored in the Nth "slot" of the pg_statistic row
+staopN: An operator used to derive the statistics stored in the Nth "slot". For example, a histogram slot would show the < operator that defines the sort order of the data
+stanumbersN: Numerical statistics of the appropriate kind for the Nth "slot", or NULL if the slot kind does not involve numerical values
+stavaluesN: Column data values of the appropriate kind for the Nth "slot", or NULL if the slot kind does not store any data values. Each array's element values are actually of the specific column's data type, so there is no way to define these columns' type more specifically than anyarray

--- 8.1
+++ 8.2
@@ -1,10 +1,10 @@
 (relation) 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. pg_stats is also designed to present the information in a more readable format than the underlying catalog — at the cost that its schema must be extended whenever new slot types are defined for pg_statistic.
-schemaname: name of schema containing table
-tablename: name of table
-attname: name of the column described by this row
-null_frac: fraction of column entries that are null
-avg_width: average width in bytes of column's entries
-n_distinct: If greater than zero, the estimated number of distinct values in the column. If less than zero, the negative of the number of distinct values divided by the number of rows. (The negated form is used when ANALYZE believes that the number of distinct values is likely to increase as the table grows; the positive form is used when the column seems to have a fixed number of possible values.) For example, -1 indicates a unique column in which the number of distinct values is the same as the number of rows.
+schemaname: Name of schema containing table
+tablename: Name of table
+attname: Name of the column described by this row
+null_frac: Fraction of column entries that are null
+avg_width: Average width in bytes of column's entries
+n_distinct: If greater than zero, the estimated number of distinct values in the column. If less than zero, the negative of the number of distinct values divided by the number of rows. (The negated form is used when ANALYZE believes that the number of distinct values is likely to increase as the table grows; the positive form is used when the column seems to have a fixed number of possible values.) For example, -1 indicates a unique column in which the number of distinct values is the same as the number of rows
 most_common_vals: A list of the most common values in the column. (NULL if no values seem to be more common than any others.)
 most_common_freqs: A list of the frequencies of the most common values, i.e., number of occurrences of each divided by total number of rows. (NULL when most_common_vals is.)
 histogram_bounds: A list of values that divide the column's values into groups of approximately equal population. The values in most_common_vals, if present, are omitted from this histogram calculation. (This column is NULL if the column data type does not have a < operator or if the most_common_vals list accounts for the entire population.)

--- 8.1
+++ 8.2
@@ -1,8 +1,8 @@
 (relation) The view pg_tables provides access to useful information about each table in the database.
-schemaname: name of schema containing table
-tablename: name of table
-tableowner: name of table's owner
-tablespace: name of tablespace containing table (NULL if default for database)
+schemaname: Name of schema containing table
+tablename: Name of table
+tableowner: Name of table's owner
+tablespace: Name of tablespace containing table (NULL if default for database)
 hasindexes: true if table has (or recently had) any indexes
 hasrules: true if table has rules
 hastriggers: true if table has triggers

--- 8.1
+++ 8.2
@@ -2,4 +2,4 @@
 spcname: Tablespace name
 spcowner: Owner of the tablespace, usually the user who created it
 spclocation: Location (directory path) of the tablespace
-spcacl: Access privileges; see GRANT and REVOKE for details.
+spcacl: Access privileges; see GRANT and REVOKE for details

--- 8.1
+++ 8.2
@@ -0,0 +1,3 @@
+abbrev  text
+utc_offset  interval
+is_dst  boolean

--- 8.1
+++ 8.2
@@ -0,0 +1,4 @@
+name  text
+abbrev  text
+utc_offset  interval
+is_dst  boolean

--- 8.1
+++ 8.2
@@ -11,4 +11,4 @@
 tginitdeferred: True if initially deferred
 tgnargs: Number of argument strings passed to trigger function
 tgattr: Currently unused
-tgargs: Argument strings to pass to trigger, each null-terminated
+tgargs: Argument strings to pass to trigger, each NULL-terminated

--- 8.1
+++ 8.2
@@ -3,12 +3,12 @@
 typnamespace: The OID of the namespace that contains this type
 typowner: Owner of the type
 typlen: For a fixed-size type, typlen is the number of bytes in the internal representation of the type. But for a variable-length type, typlen is negative. -1 indicates a "varlena" type (one that has a length word), -2 indicates a null-terminated C string.
-typbyval: typbyval determines whether internal routines pass a value of this type by value or by reference. typbyval had better be false if typlen is not 1, 2, or 4 (or 8 on machines where Datum is 8 bytes). Variable-length types are always passed by reference. Note that typbyval can be false even if the length would allow pass-by-value; this is currently true for type float4, for example.
-typtype: typtype is b for a base type, c for a composite type (e.g., a table's row type), d for a domain, or p for a pseudo-type. See also typrelid and typbasetype.
-typisdefined: True if the type is defined, false if this is a placeholder entry for a not-yet-defined type. When typisdefined is false, nothing except the type name, namespace, and OID can be relied on.
-typdelim: Character that separates two values of this type when parsing array input. Note that the delimiter is associated with the array element data type, not the array data type.
-typrelid: If this is a composite type (see typtype), then this column points to the pg_class entry that defines the corresponding table. (For a free-standing composite type, the pg_class entry doesn't really represent a table, but it is needed anyway for the type's pg_attribute entries to link to.) Zero for non-composite types.
-typelem: If typelem is not 0 then it identifies another row in pg_type. The current type can then be subscripted like an array yielding values of type typelem. A "true" array type is variable length (typlen = -1), but some fixed-length (typlen > 0) types also have nonzero typelem, for example name and point. If a fixed-length type has a typelem then its internal representation must be some number of values of the typelem data type with no other data. Variable-length array types have a header defined by the array subroutines.
+typbyval: typbyval determines whether internal routines pass a value of this type by value or by reference. typbyval had better be false if typlen is not 1, 2, or 4 (or 8 on machines where Datum is 8 bytes). Variable-length types are always passed by reference. Note that typbyval can be false even if the length would allow pass-by-value; this is currently true for type float4, for example
+typtype: typtype is b for a base type, c for a composite type (e.g., a table's row type), d for a domain, or p for a pseudo-type. See also typrelid and typbasetype
+typisdefined: True if the type is defined, false if this is a placeholder entry for a not-yet-defined type. When typisdefined is false, nothing except the type name, namespace, and OID can be relied on
+typdelim: Character that separates two values of this type when parsing array input. Note that the delimiter is associated with the array element data type, not the array data type
+typrelid: If this is a composite type (see typtype), then this column points to the pg_class entry that defines the corresponding table. (For a free-standing composite type, the pg_class entry doesn't really represent a table, but it is needed anyway for the type's pg_attribute entries to link to.) Zero for non-composite types
+typelem: If typelem is not 0 then it identifies another row in pg_type. The current type can then be subscripted like an array yielding values of type typelem. A "true" array type is variable length (typlen = -1), but some fixed-length (typlen > 0) types also have nonzero typelem, for example name and point. If a fixed-length type has a typelem then its internal representation must be some number of values of the typelem data type with no other data. Variable-length array types have a header defined by the array subroutines
 typinput: Input conversion function (text format)
 typoutput: Output conversion function (text format)
 typreceive: Input conversion function (binary format), or 0 if none
@@ -16,9 +16,9 @@
 typanalyze: Custom ANALYZE function, or 0 to use the standard function
 typalign: typalign is the alignment required when storing a value of this type. It applies to storage on disk as well as most representations of the value inside PostgreSQL. When multiple values are stored consecutively, such as in the representation of a complete row on disk, padding is inserted before a datum of this type so that it begins on the specified boundary. The alignment reference is the beginning of the first datum in the sequence. Possible values are: c = char alignment, i.e., no alignment needed. s = short alignment (2 bytes on most machines). i = int alignment (4 bytes on most machines). d = double alignment (8 bytes on many machines, but by no means all). Note: For types used in system tables, it is critical that the size and alignment defined in pg_type agree with the way that the compiler will lay out the column in a structure representing a table row.
 typstorage: typstorage tells for varlena types (those with typlen = -1) if the type is prepared for toasting and what the default strategy for attributes of this type should be. Possible values are p: Value must always be stored plain. e: Value can be stored in a "secondary" relation (if relation has one, see pg_class.reltoastrelid). m: Value can be stored compressed inline. x: Value can be stored compressed inline or stored in "secondary" storage. Note that m columns can also be moved out to secondary storage, but only as a last resort (e and x columns are moved first).
-typnotnull: typnotnull represents a not-null constraint on a type. Used for domains only.
-typbasetype: If this is a domain (see typtype), then typbasetype identifies the type that this one is based on. Zero if not a domain.
-typtypmod: Domains use typtypmod to record the typmod to be applied to their base type (-1 if base type does not use a typmod). -1 if this type is not a domain.
-typndims: typndims is the number of array dimensions for a domain that is an array (that is, typbasetype is an array type; the domain's typelem will match the base type's typelem). Zero for types other than array domains.
-typdefaultbin: If typdefaultbin is not null, it is the nodeToString() representation of a default expression for the type. This is only used for domains.
-typdefault: typdefault is null if the type has no associated default value. If typdefaultbin is not null, typdefault must contain a human-readable version of the default expression represented by typdefaultbin. If typdefaultbin is null and typdefault is not, then typdefault is the external representation of the type's default value, which may be fed to the type's input converter to produce a constant.
+typnotnull: typnotnull represents a not-null constraint on a type. Used for domains only
+typbasetype: If this is a domain (see typtype), then typbasetype identifies the type that this one is based on. Zero if this type is not a domain
+typtypmod: Domains use typtypmod to record the typmod to be applied to their base type (-1 if base type does not use a typmod). -1 if this type is not a domain
+typndims: typndims is the number of array dimensions for a domain that is an array (that is, typbasetype is an array type; the domain's typelem will match the base type's typelem). Zero for types other than array domains
+typdefaultbin: If typdefaultbin is not null, it is the nodeToString() representation of a default expression for the type. This is only used for domains
+typdefault: typdefault is null if the type has no associated default value. If typdefaultbin is not null, typdefault must contain a human-readable version of the default expression represented by typdefaultbin. If typdefaultbin is null and typdefault is not, then typdefault is the external representation of the type's default value, which may be fed to the type's input converter to produce a constant

--- 8.1
+++ 8.2
@@ -1,5 +1,5 @@
 (relation) The view pg_views provides access to useful information about each view in the database.
-schemaname: name of schema containing view
-viewname: name of view
-viewowner: name of view's owner
-definition: view definition (a reconstructed SELECT query)
+schemaname: Name of schema containing view
+viewname: Name of view
+viewowner: Name of view's owner
+definition: View definition (a reconstructed SELECT query)