There are patch queue comments suggesting the removal of the ipcclean
command-line utility. ipcclean doesn't work on Windows, and it probably
doesn't work perfectly all Unixes either.
The attached patch removes the utility, though some files will have to
be removed as well.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Index: doc/src/sgml/array.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/array.sgml,v
retrieving revision 1.62
diff -c -c -r1.62 array.sgml
*** doc/src/sgml/array.sgml 7 Jun 2007 14:49:56 -0000 1.62
--- doc/src/sgml/array.sgml 26 Mar 2008 14:42:14 -0000
***************
*** 258,263 ****
--- 258,266 ----
{{meeting,lunch},{training,presentation}}
(1 row)
</programlisting>
+
+ To avoid confusion with slices, use slice syntax for all dimmension
+ references, e.g. <literal>[1:2][1:1]</>, not <literal>[2][1:1]</>.
</para>
<para>
***************
*** 275,281 ****
any of the subscript expressions are null. However, in other corner
cases such as selecting an array slice that
is completely outside the current array bounds, a slice expression
! yields an empty (zero-dimensional) array instead of null.
If the requested slice partially overlaps the array bounds, then it
is silently reduced to just the overlapping region.
</para>
--- 278,285 ----
any of the subscript expressions are null. However, in other corner
cases such as selecting an array slice that
is completely outside the current array bounds, a slice expression
! yields an empty (zero-dimensional) array instead of null. (This
! does not match non-slice behavior and is done for historical reasons.)
If the requested slice partially overlaps the array bounds, then it
is silently reduced to just the overlapping region.
</para>
