Move a few release note items from "Utility Commands" to "Object Manipulation".

diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
index 45fe82f4004916594fb64a200f7fc6db2d5ec91c..b92b067c4ae09dc66fd010cc145d7368e542559a 100644 (file)
--- a/doc/src/sgml/release.sgml
+++ b/doc/src/sgml/release.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.573 2008/01/01 19:36:20 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.574 2008/01/01 19:41:14 momjian Exp $ -->
 <!--
 
 Typical markup:
@@ -1463,6 +1463,43 @@ current_date &lt; 2017-11-17
       </para>
      </listitem>
 
+     <listitem>
+      <para>
+       Implement <command>CREATE TABLE LIKE ...  INCLUDING
+       INDEXES</command> (Trevor Hardcastle, Nikhil Sontakke, Neil)
+      </para>
+     </listitem>
+
+     <listitem>
+      <para>
+       Allow <command>CREATE INDEX CONCURRENTLY</command> to ignore
+       transactions in other databases (Simon)
+      </para>
+     </listitem>
+
+     <listitem>
+      <para>
+       Add <command>ALTER VIEW ... RENAME TO</command> and <command>ALTER
+       SEQUENCE ... RENAME TO</command> (David Fetter, Neil)
+      </para>
+
+      <para>
+       Previously this could only be done via <command>ALTER TABLE ...
+       RENAME TO</command>.
+      </para>
+     </listitem>
+
+     <listitem>
+      <para>
+       Make <command>CREATE/DROP/RENAME DATABASE</> wait briefly for
+       conflicting backends to exit before failing (Tom)
+      </para>
+
+      <para>
+       This increases the likelihood that these commands will succeed.
+      </para>
+     </listitem>
+
      <listitem>
       <para>
        Allow triggers and rules to be deactivated in groups using a
@@ -1537,32 +1574,6 @@ current_date &lt; 2017-11-17
       </para>
      </listitem>
 
-     <listitem>
-      <para>
-       Add <command>ALTER VIEW ... RENAME TO</command> and <command>ALTER
-       SEQUENCE ... RENAME TO</command> (David Fetter, Neil)
-      </para>
-
-      <para>
-       Previously this could only be done via <command>ALTER TABLE ...
-       RENAME TO</command>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Implement <command>CREATE TABLE LIKE ...  INCLUDING
-       INDEXES</command> (Trevor Hardcastle, Nikhil Sontakke, Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <command>CREATE INDEX CONCURRENTLY</command> to ignore
-       transactions in other databases (Simon)
-      </para>
-     </listitem>
-
      <listitem>
       <para>
        Make <command>CLUSTER</command> MVCC-safe (Heikki Linnakangas)
@@ -1601,17 +1612,6 @@ current_date &lt; 2017-11-17
       </para>
      </listitem>
 
-     <listitem>
-      <para>
-       Make <command>CREATE/DROP/RENAME DATABASE</> wait briefly for
-       conflicting backends to exit before failing (Tom)
-      </para>
-
-      <para>
-       This increases the likelihood that these commands will succeed.
-      </para>
-     </listitem>
-
      <listitem>
       <para>
        Limit the amount of information reported when a user is dropped