What changed?

9.3 → 9.4
+ aggkind  "char"
+ aggnumdirectargs  smallint
+ aggmtransfn  regproc
+ aggminvtransfn  regproc
+ aggmfinalfn  regproc
+ aggfinalextra  boolean
+ aggmfinalextra  boolean
+ aggtransspace  integer
+ aggmtranstype  oid
+ aggmtransspace  integer
+ aggminitval  text

--- 9.3
+++ 9.4
@@ -1,4 +1,4 @@
-(relation) The catalog pg_am stores information about index access methods. There is one row for each index access method supported by the system. The contents of this catalog are discussed in detail in Chapter 54.
+(relation) The catalog pg_am stores information about index access methods. There is one row for each index access method supported by the system. The contents of this catalog are discussed in detail in Chapter 55.
 oid: Row identifier (hidden attribute; must be explicitly selected)
 amname: Name of the access method
 amstrategies: Number of operator strategies for this access method, or zero if access method does not have a fixed set of operator strategies

--- 9.3
+++ 9.4
@@ -7,4 +7,4 @@
 amoppurpose: Operator purpose, either s for search or o for ordering
 amopopr: OID of the operator
 amopmethod: Index access method operator family is for
-amopsortfamily: The btree operator family this entry sorts according to, if an ordering operator; zero if a search operator
+amopsortfamily: The B-tree operator family this entry sorts according to, if an ordering operator; zero if a search operator

9.3 → 9.4
+ relreplident  "char"
- reltoastidxid  oid

--- 9.3
+++ 9.4
@@ -1,4 +1,4 @@
-(relation) The pg_cursors view lists the cursors that are currently available. Cursors can be defined in several ways: via the DECLARE statement in SQL via the Bind message in the frontend/backend protocol, as described in Section 48.2.3 via the Server Programming Interface (SPI), as described in Section 44.1 The pg_cursors view displays cursors created by any of these means. Cursors only exist for the duration of the transaction that defines them, unless they have been declared WITH HOLD. Therefore non-holdable cursors are only present in the view until the end of their creating transaction.
+(relation) The pg_cursors view lists the cursors that are currently available. Cursors can be defined in several ways: via the DECLARE statement in SQL via the Bind message in the frontend/backend protocol, as described in Section 49.2.3 via the Server Programming Interface (SPI), as described in Section 44.1 The pg_cursors view displays cursors created by any of these means. Cursors only exist for the duration of the transaction that defines them, unless they have been declared WITH HOLD. Therefore non-holdable cursors are only present in the view until the end of their creating transaction.
 name: The name of the cursor
 statement: The verbatim query string submitted to declare this cursor
 is_holdable: true if the cursor is holdable (that is, it can be accessed after the transaction that declared the cursor has committed); false otherwise

--- 9.3
+++ 9.4
@@ -5,7 +5,7 @@
 encoding: Character encoding for this database (pg_encoding_to_char() can translate this number to the encoding name)
 datcollate: LC_COLLATE for this database
 datctype: LC_CTYPE for this database
-datistemplate: If true then this database can be used in the TEMPLATE clause of CREATE DATABASE to create a new database as a clone of this one
+datistemplate: If true, then this database can be cloned by any user with CREATEDB privileges; if false, then only superusers or the owner of the database can clone it.
 datallowconn: If false then no one can connect to this database. This is used to protect the template0 database from being altered.
 datconnlimit: Sets maximum number of concurrent connections that can be made to this database. -1 means no limit.
 datlastsysoid: Last system OID in the database; useful particularly to pg_dump

9.3 → 9.4
+ indisreplident  boolean

--- 9.3
+++ 9.4
@@ -0,0 +1,9 @@
+slot_name  name
+plugin  name
+slot_type  text
+datoid  oid
+database  text
+active  boolean
+xmin  xid
+catalog_xmin  xid
+restart_lsn  pg_lsn

9.3 → 9.4
- ev_attr  smallint

--- 9.3
+++ 9.4
@@ -1,4 +1,4 @@
-(relation) The catalog pg_seclabel stores security labels on database objects. Security labels can be manipulated with the SECURITY LABEL command. For an easier way to view security labels, see Section 47.65. See also pg_shseclabel, which performs a similar function for security labels of database objects that are shared across a database cluster.
+(relation) The catalog pg_seclabel stores security labels on database objects. Security labels can be manipulated with the SECURITY LABEL command. For an easier way to view security labels, see Section 48.66. See also pg_shseclabel, which performs a similar function for security labels of database objects that are shared across a database cluster.
 objoid: The OID of the object this security label pertains to
 classoid: The OID of the system catalog this object appears in
 objsubid: For a security label 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.

--- 9.3
+++ 9.4
@@ -1,4 +1,4 @@
-(relation) The catalog pg_shseclabel stores security labels on shared database objects. Security labels can be manipulated with the SECURITY LABEL command. For an easier way to view security labels, see Section 47.65. See also pg_seclabel, which performs a similar function for security labels involving objects within a single database. Unlike most system catalogs, pg_shseclabel is shared across all databases of a cluster: there is only one copy of pg_shseclabel per cluster, not one per database.
+(relation) The catalog pg_shseclabel stores security labels on shared database objects. Security labels can be manipulated with the SECURITY LABEL command. For an easier way to view security labels, see Section 48.66. See also pg_seclabel, which performs a similar function for security labels involving objects within a single database. Unlike most system catalogs, pg_shseclabel is shared across all databases of a cluster: there is only one copy of pg_shseclabel per cluster, not one per database.
 objoid: The OID of the object this security label pertains to
 classoid: The OID of the system catalog this object appears in
 provider: The label provider associated with this label.

9.3 → 9.4
+ backend_xid  xid
+ backend_xmin  xid

9.3 → 9.4
+ n_mod_since_analyze  bigint

--- 9.3
+++ 9.4
@@ -0,0 +1,7 @@
+archived_count  bigint
+last_archived_wal  text
+last_archived_time  timestamp with time zone
+failed_count  bigint
+last_failed_wal  text
+last_failed_time  timestamp with time zone
+stats_reset  timestamp with time zone

9.3 → 9.4
+ backend_xmin  xid
~ flush_location  text → pg_lsn
~ replay_location  text → pg_lsn
~ sent_location  text → pg_lsn
~ write_location  text → pg_lsn

9.3 → 9.4
+ n_mod_since_analyze  bigint

9.3 → 9.4
+ n_mod_since_analyze  bigint

--- 9.3
+++ 9.4
@@ -8,5 +8,5 @@
 idx_blks_hit: Number of buffer hits in all indexes on this table
 toast_blks_read: Number of disk blocks read from this table's TOAST table (if any)
 toast_blks_hit: Number of buffer hits in this table's TOAST table (if any)
-tidx_blks_read: Number of disk blocks read from this table's TOAST table index (if any)
-tidx_blks_hit: Number of buffer hits in this table's TOAST table index (if any)
+tidx_blks_read: Number of disk blocks read from this table's TOAST table indexes (if any)
+tidx_blks_hit: Number of buffer hits in this table's TOAST table indexes (if any)

--- 9.3
+++ 9.4
@@ -8,5 +8,5 @@
 idx_blks_hit: Number of buffer hits in all indexes on this table
 toast_blks_read: Number of disk blocks read from this table's TOAST table (if any)
 toast_blks_hit: Number of buffer hits in this table's TOAST table (if any)
-tidx_blks_read: Number of disk blocks read from this table's TOAST table index (if any)
-tidx_blks_hit: Number of buffer hits in this table's TOAST table index (if any)
+tidx_blks_read: Number of disk blocks read from this table's TOAST table indexes (if any)
+tidx_blks_hit: Number of buffer hits in this table's TOAST table indexes (if any)

--- 9.3
+++ 9.4
@@ -8,5 +8,5 @@
 idx_blks_hit: Number of buffer hits in all indexes on this table
 toast_blks_read: Number of disk blocks read from this table's TOAST table (if any)
 toast_blks_hit: Number of buffer hits in this table's TOAST table (if any)
-tidx_blks_read: Number of disk blocks read from this table's TOAST table index (if any)
-tidx_blks_hit: Number of buffer hits in this table's TOAST table index (if any)
+tidx_blks_read: Number of disk blocks read from this table's TOAST table indexes (if any)
+tidx_blks_hit: Number of buffer hits in this table's TOAST table indexes (if any)

--- 9.3
+++ 9.4
@@ -7,7 +7,7 @@
 tgenabled: Controls in which session_replication_role modes the trigger fires. O = trigger fires in "origin" and "local" modes, D = trigger is disabled, R = trigger fires in "replica" mode, A = trigger fires always.
 tgisinternal: True if trigger is internally generated (usually, to enforce the constraint identified by tgconstraint)
 tgconstrrelid: The table referenced by a referential integrity constraint
-tgconstrindid: The index supporting a unique, primary key, or referential integrity constraint
+tgconstrindid: The index supporting a unique, primary key, referential integrity, or exclusion constraint
 tgconstraint: The pg_constraint entry associated with the trigger, if any
 tgdeferrable: True if constraint trigger is deferrable
 tginitdeferred: True if constraint trigger is initially deferred

--- 9.3
+++ 9.4
@@ -6,7 +6,7 @@
 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.
 typtype: typtype is b for a base type, c for a composite type (e.g., a table's row type), d for a domain, e for an enum type, p for a pseudo-type, or r for a range type. See also typrelid and typbasetype.
-typcategory: typcategory is an arbitrary classification of data types that is used by the parser to determine which implicit casts should be "preferred". See Table 47-52.
+typcategory: typcategory is an arbitrary classification of data types that is used by the parser to determine which implicit casts should be "preferred". See Table 48-53.
 typispreferred: True if the type is a preferred cast target within its typcategory
 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.