Index: openacs-4/contrib/obsolete-packages/bboard/www/message-threaded-postgresql.xql
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/contrib/obsolete-packages/bboard/www/message-threaded-postgresql.xql,v
diff -u -N -r1.2 -r1.3
--- openacs-4/contrib/obsolete-packages/bboard/www/message-threaded-postgresql.xql	1 Dec 2001 22:25:58 -0000	1.2
+++ openacs-4/contrib/obsolete-packages/bboard/www/message-threaded-postgresql.xql	9 Dec 2001 21:08:31 -0000	1.3
@@ -33,7 +33,7 @@
      and m.tree_sortkey between m2.tree_sortkey and tree_right(m2.tree_sortkey)
      and p.person_id = m.sender
      and m.message_id = bfmm.message_id 
-   order by m.sent_date
+   order by m.tree_sortkey
 
       </querytext>
 </fullquery>
Index: openacs-4/packages/acs-kernel/sql/postgresql/postgresql.sql
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-kernel/sql/postgresql/postgresql.sql,v
diff -u -N -r1.18 -r1.19
--- openacs-4/packages/acs-kernel/sql/postgresql/postgresql.sql	9 Dec 2001 04:21:58 -0000	1.18
+++ openacs-4/packages/acs-kernel/sql/postgresql/postgresql.sql	9 Dec 2001 21:08:31 -0000	1.19
@@ -290,7 +290,7 @@
 
 -- 2. Storage is one byte per level for each level in the tree that
 --    has fewer than 128 nodes.  If more nodes exist at a given level
---    two bytes are occupied.  The old scheme used three bytes per
+--    two bytes are required.  The old scheme used three bytes per
 --    level.  Along with saving space in data tables, this will speed
 --    key comparisons during index scans and increases the number of
 --    keys stored in any given index page.
@@ -541,8 +541,12 @@
 -- Rather than use the general solution I have just hacked up a PL/pgSQL function to
 -- create the one recursive function we need: tree_ancestor_keys(varbit, integer).
 
+-- tree_ancestor_keys(varbit, integer) returns the set of ancestor keys starting at
+-- the level passed in as the second parameter down to the key passed in as the first
+
 -- This function should probably only be called from its overloaded cousin
--- tree_ancestor_keys(varbit).
+-- tree_ancestor_keys(varbit), which returns the set of tree_sortkeys for all of the
+-- given tree_sortkey's ancestors..
 
 begin
 
@@ -579,16 +583,14 @@
 
 create function tree_ancestor_keys(varbit) returns setof varbit as '
 
--- tree_ancestor_keys returns the set of ancestor keys starting at the level passed
--- in as the second parameter down to the key passed in as the first parameter.  Normally
--- this will be one - its intended use is to drive the recursive building of the set of
--- ancestor keys.
+-- Return the set of tree_sortkeys for all of the given tree_sortkey's
+-- ancestors.
 
 -- Here is an example on acs_objects:
 
 -- select o.*
 -- from acs_objects o,
---   (select tree_ancestor_keys(acs_objects_get_tree_sortkey(:object_id), 1) as tree_sortkey) parents
+--   (select tree_ancestor_keys(acs_objects_get_tree_sortkey(:object_id)) as tree_sortkey) parents
 -- where o.tree_sortkey = parents.tree_sortkey;
 
 -- This query will use the index on tree_sortkey to scan acs_objects.  The function to grab
@@ -603,7 +605,7 @@
 -- select o.*
 -- from acs_objects o,
 --     (select tree_sortkey from acs_objects where object_id = :root_id) as root
---   (select tree_ancestor_keys(acs_objects_get_tree_sortkey(:object_id), 1) as tree_sortkey) parents
+--   (select tree_ancestor_keys(acs_objects_get_tree_sortkey(:object_id)) as tree_sortkey) parents
 -- where o.tree_sortkey = parents.tree_sortkey
 --   and o.tree_sortkey >= root.tree_sortkey;
 
@@ -621,8 +623,8 @@
 -- performance.   
 
 -- WARNING: subselects in where clauses that call this function and join on an outer table appear
--- to reliably kill PG 7.1.2.   Not tested for PG 7.2.  If it fails there a bug report will be
--- filed.
+-- to reliably kill PG 7.1.2, at least if "exists" is involved.   Not tested for PG 7.2.  If it
+-- fails there a bug report will be filed.
 
   select tree_ancestor_keys($1, 1)
 
Index: openacs-4/packages/acs-messaging/sql/postgresql/acs-messaging-create.sql
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-messaging/sql/postgresql/acs-messaging-create.sql,v
diff -u -N -r1.7 -r1.8
--- openacs-4/packages/acs-messaging/sql/postgresql/acs-messaging-create.sql	9 Dec 2001 04:21:58 -0000	1.7
+++ openacs-4/packages/acs-messaging/sql/postgresql/acs-messaging-create.sql	9 Dec 2001 21:08:31 -0000	1.8
@@ -67,6 +67,7 @@
 create index acs_messages_tree_skey_idx on acs_messages (tree_sortkey);
 create index acs_messages_reply_to_idx on acs_messages (reply_to);
 create index acs_messages_sender_idx on acs_messages (sender);
+create index acs_messages_sent_idx on acs_messages (sent_date);
 
 comment on table acs_messages is '
     A generic message which may be attached to any object in the system.
Index: openacs-4/packages/file-storage/tcl/file-storage-procs-postgresql.xql
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/file-storage/tcl/file-storage-procs-postgresql.xql,v
diff -u -N -r1.8 -r1.9
--- openacs-4/packages/file-storage/tcl/file-storage-procs-postgresql.xql	9 Dec 2001 04:21:58 -0000	1.8
+++ openacs-4/packages/file-storage/tcl/file-storage-procs-postgresql.xql	9 Dec 2001 21:08:31 -0000	1.9
@@ -81,7 +81,7 @@
           cr_items i
         where i.tree_sortkey = parents.tree_sortkey
           and i.tree_sortkey > root.tree_sortkey
-    	order by j.tree_sortkey asc
+    	order by i.tree_sortkey asc
 
       </querytext>
 </fullquery>