From: Peter Eisentraut <peter_e@gmx.net>
Date: Sun, 22 May 2011 19:21:37 +0000 (+0300)
Subject: Put lists in sensible order
X-Git-Tag: REL9_1_BETA2~91
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=60497722ac6d69d8ff82fe328b0a128e73433bec;p=postgresql

Put lists in sensible order
---

diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml
index eba3a0a25d..2febb4ced8 100644
--- a/doc/src/sgml/information_schema.sgml
+++ b/doc/src/sgml/information_schema.sgml
@@ -34,13 +34,13 @@
   </para>
 
   <para>
-   This problem can appear when querying information schema views like
-   <literal>referential_constraints</>, <literal>check_constraints</>,
-   <literal>domain_constraints</>, and
-   <literal>check_constraint_routine_usage</>.  Some other views have
-   similar issues but contain the table name to help distinguish
-   duplicate rows, e.g. <literal>table_constraints</>,
-   <literal>constraint_table_usage</>, <literal>constraint_column_usage</>.
+   This problem can appear when querying information schema views such
+   as <literal>check_constraint_routine_usage</>,
+   <literal>check_constraints</>, <literal>domain_constraints</>, and
+   <literal>referential_constraints</>.  Some other views have similar
+   issues but contain the table name to help distinguish duplicate
+   rows, e.g., <literal>constraint_column_usage</>,
+   <literal>constraint_table_usage</>, <literal>table_constraints</>.
   </para>
  </note>