Add an explicit comment about POSIX time zone names having the reverse

sign convention from everyplace else in Postgres.  I don't suppose that
this will stop people from being confused, but at least we can say that
it's documented.

diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index 507b4b6142c348dfc48d695b7c129fd29f916d3a..e1fb7d42493469ee325ad205b3a2822f718b9e29 100644 (file)
--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.199 2007/05/03 15:05:56 neilc Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.200 2007/05/08 17:02:59 tgl Exp $ -->
 
  <chapter id="datatype">
   <title id="datatype-title">Data Types</title>
@@ -2275,6 +2275,11 @@ January 8 04:05:06 1999 PST
      reasonableness of the zone abbreviations.  For example, <literal>SET
      TIMEZONE TO FOOBAR0</> will work, leaving the system effectively using
      a rather peculiar abbreviation for UTC.
+     Another issue to keep in mind is that in POSIX time zone names,
+     positive offsets are used for locations <emphasis>west</> of Greenwich.
+     Everywhere else, <productname>PostgreSQL</productname> follows the
+     ISO-8601 convention that positive timezone offsets are <emphasis>east</>
+     of Greenwich.
     </para>
 
     <para>