Adjust chapter ordering in Internals part to something that seems more

reasonable.

doc/src/sgml/arch-dev.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.20 2003/06/22 05:48:26 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.21 2003/06/22 16:16:44 tgl Exp $
 -->
 
  <chapter id="overview">
@@ -437,7 +437,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.20 2003/06/22 05:48:26 tg
    <para>
     The <firstterm>executor</firstterm> takes the plan handed back by the
     planner/optimizer and recursively processes it to extract the required set
-    of rows.  This is essentially a demand-driven pipeline mechanism.
+    of rows.  This is essentially a demand-pull pipeline mechanism.
     Each time a plan node is called, it must deliver one more tuple, or
     report that it is done delivering tuples.
    </para>

doc/src/sgml/postgres.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/postgres.sgml,v 1.52 2003/05/18 20:55:56 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/postgres.sgml,v 1.53 2003/06/22 16:16:44 tgl Exp $
 -->
 
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [
@@ -237,15 +237,15 @@ $Header: /cvsroot/pgsql/doc/src/sgml/postgres.sgml,v 1.52 2003/05/18 20:55:56 pe
    </para>
   </partintro>
 
-  &sources;
   &arch-dev;
   &catalogs;
   &protocol;
-  &compiler;
-  &bki;
   &page;
   &geqo;
   &gist;
+  &bki;
+  &sources;
+  &compiler;
   &nls;
 
  </part>