Improve documentation for odd array slice behavior.

diff --git a/doc/src/sgml/array.sgml b/doc/src/sgml/array.sgml
index bf93315ec2c58263e11ee5e08eb1cd71080e6aaa..3f7e5d9a3e6304d65bc1e4a4fe01637344dd83df 100644 (file)
--- a/doc/src/sgml/array.sgml
+++ b/doc/src/sgml/array.sgml
@@ -258,6 +258,9 @@ SELECT schedule[1:2][2] FROM sal_emp WHERE name = 'Bill';
  {{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,7 +278,8 @@ SELECT schedule[1:2][2] FROM sal_emp WHERE name = 'Bill';
   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.
+  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>