From 140b0626e882316386ed422b160d6435467ca1f6 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 30 Dec 2013 13:27:54 -0500 Subject: [PATCH] Fix alphabetization in catalogs.sgml. Some recent patches seem not to have grasped the concept that the catalogs are described in alphabetical order. --- doc/src/sgml/catalogs.sgml | 293 +++++++++++++++++++------------------ 1 file changed, 147 insertions(+), 146 deletions(-) diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index 09f7e40b29..ebde12dee8 100644 --- a/doc/src/sgml/catalogs.sgml +++ b/doc/src/sgml/catalogs.sgml @@ -99,13 +99,13 @@ - pg_constraint - check constraints, unique constraints, primary key constraints, foreign key constraints + pg_collation + collations (locale information) - pg_collation - collations (locale information) + pg_constraint + check constraints, unique constraints, primary key constraints, foreign key constraints @@ -1933,20 +1933,22 @@ - - <structname>pg_event_trigger</structname> + + <structname>pg_collation</structname> - - pg_event_trigger + + pg_collation - The catalog pg_event_trigger stores event triggers. - See for more information. + The catalog pg_collation describes the + available collations, which are essentially mappings from an SQL + name to operating system locale categories. + See for more information. - <structname>pg_event_trigger</> Columns + <structname>pg_collation</> Columns @@ -1960,59 +1962,83 @@ - evtname - name + oid + oid - Trigger name (must be unique) + Row identifier (hidden attribute; must be explicitly selected) - evtevent + collname name - Identifies the event for which this trigger fires + Collation name (unique per namespace and encoding) - evtowner + collnamespace oid - pg_authid.oid - Owner of the event trigger + pg_namespace.oid + + The OID of the namespace that contains this collation + - evtfoid + collowner oid - pg_proc.oid - The function to be called + pg_authid.oid + Owner of the collation - evtenabled - char + collencoding + int4 - - Controls in which modes - the event trigger fires. - O = trigger fires in origin and local modes, - D = trigger is disabled, - R = trigger fires in replica mode, - A = trigger fires always. - + Encoding in which the collation is applicable, or -1 if it + works for any encoding - evttags - text[] + collcollate + name - - Command tags for which this trigger will fire. If NULL, the firing - of this trigger is not restricted on the basis of the command tag. - + LC_COLLATE for this collation object + + + + collctype + name + + LC_CTYPE for this collation object
+ + + Note that the unique key on this catalog is (collname, + collencoding, collnamespace) not just + (collname, collnamespace). + PostgreSQL generally ignores all + collations that do not have collencoding equal to + either the current database's encoding or -1, and creation of new entries + with the same name as an entry with collencoding = -1 + is forbidden. Therefore it is sufficient to use a qualified SQL name + (schema.name) to identify a collation, + even though this is not unique according to the catalog definition. + The reason for defining the catalog this way is that + initdb fills it in at cluster initialization time with + entries for all locales available on the system, so it must be able to + hold entries for all encodings that might ever be used in the cluster. + + + + In the template0 database, it could be useful to create + collations whose encoding does not match the database encoding, + since they could match the encodings of databases later cloned from + template0. This would currently have to be done manually. + @@ -2296,116 +2322,8 @@ relation. - - - <structname>pg_collation</structname> - - - pg_collation - - - - The catalog pg_collation describes the - available collations, which are essentially mappings from an SQL - name to operating system locale categories. - See for more information. - - - - <structname>pg_collation</> Columns - - - - - Name - Type - References - Description - - - - - - oid - oid - - Row identifier (hidden attribute; must be explicitly selected) - - - - collname - name - - Collation name (unique per namespace and encoding) - - - - collnamespace - oid - pg_namespace.oid - - The OID of the namespace that contains this collation - - - - - collowner - oid - pg_authid.oid - Owner of the collation - - - - collencoding - int4 - - Encoding in which the collation is applicable, or -1 if it - works for any encoding - - - - collcollate - name - - LC_COLLATE for this collation object - - - - collctype - name - - LC_CTYPE for this collation object - - - -
- - - Note that the unique key on this catalog is (collname, - collencoding, collnamespace) not just - (collname, collnamespace). - PostgreSQL generally ignores all - collations that do not have collencoding equal to - either the current database's encoding or -1, and creation of new entries - with the same name as an entry with collencoding = -1 - is forbidden. Therefore it is sufficient to use a qualified SQL name - (schema.name) to identify a collation, - even though this is not unique according to the catalog definition. - The reason for defining the catalog this way is that - initdb fills it in at cluster initialization time with - entries for all locales available on the system, so it must be able to - hold entries for all encodings that might ever be used in the cluster. - - - - In the template0 database, it could be useful to create - collations whose encoding does not match the database encoding, - since they could match the encodings of databases later cloned from - template0. This would currently have to be done manually. - - <structname>pg_conversion</structname> @@ -3178,6 +3096,89 @@ + + <structname>pg_event_trigger</structname> + + + pg_event_trigger + + + + The catalog pg_event_trigger stores event triggers. + See for more information. + + + + <structname>pg_event_trigger</> Columns + + + + + Name + Type + References + Description + + + + + + evtname + name + + Trigger name (must be unique) + + + + evtevent + name + + Identifies the event for which this trigger fires + + + + evtowner + oid + pg_authid.oid + Owner of the event trigger + + + + evtfoid + oid + pg_proc.oid + The function to be called + + + + evtenabled + char + + + Controls in which modes + the event trigger fires. + O = trigger fires in origin and local modes, + D = trigger is disabled, + R = trigger fires in replica mode, + A = trigger fires always. + + + + + evttags + text[] + + + Command tags for which this trigger will fire. If NULL, the firing + of this trigger is not restricted on the basis of the command tag. + + + + +
+ + + <structname>pg_extension</structname> -- 2.40.0