diff -cr cvs/pgsql/doc/src/sgml/datatype.sgml cvs.build/pgsql/doc/src/sgml/datatype.sgml
*** cvs/pgsql/doc/src/sgml/datatype.sgml	2006-06-19 03:25:38.000000000 +0200
--- cvs.build/pgsql/doc/src/sgml/datatype.sgml	2006-06-20 00:40:57.000000000 +0200
***************
*** 1602,1608 ****
        linkend="datatype-datetime-time-table"> 
        and <xref linkend="datatype-timezone-table">.)  If a time zone is
        specified in the input for <type>time without time zone</type>,
!       it is silently ignored.
       </para>
  
        <table id="datatype-datetime-time-table">
--- 1602,1613 ----
        linkend="datatype-datetime-time-table"> 
        and <xref linkend="datatype-timezone-table">.)  If a time zone is
        specified in the input for <type>time without time zone</type>,
!       it is silently ignored. You can also always specify a date but it will
!       be ignored except for when you use a full time zone name like
!       <literal>America/New_York</literal>. In this case specifying the date
!       is compulsory in order to tell which time zone offset should be
!       applied. It will be applied whatever time zone offset was valid at that
!       date and time at the specified place.
       </para>
  
        <table id="datatype-datetime-time-table">
***************
*** 1659,1664 ****
--- 1664,1673 ----
            <entry><literal>04:05:06 PST</literal></entry>
            <entry>time zone specified by name</entry>
           </row>
+          <row>
+           <entry><literal>2003-04-12 04:05:06 America/New_York</literal></entry>
+           <entry>time zone specified by full name</entry>
+          </row>
          </tbody>
         </tgroup>
        </table>
***************
*** 1678,1683 ****
--- 1687,1696 ----
            <entry>Pacific Standard Time</entry>
           </row>
           <row>
+           <entry><literal>America/New_York</literal></entry>
+           <entry>Full time zone name</entry>
+          </row>
+          <row>
            <entry><literal>-8:00</literal></entry>
            <entry>ISO-8601 offset for PST</entry>
           </row>
***************
*** 1739,1746 ****
  </programlisting>
  
        are valid values, which follow the <acronym>ISO</acronym> 8601
!       standard.  In addition, the wide-spread format
  
  <programlisting>
  January 8 04:05:06 1999 PST
  </programlisting>
--- 1752,1763 ----
  </programlisting>
  
        are valid values, which follow the <acronym>ISO</acronym> 8601
!       standard. You can also specify the full time zone name as in
! <programlisting>
! 1999-01-08 04:05:06 America/New_York
! </programlisting>
  
+       In addition, the wide-spread format
  <programlisting>
  January 8 04:05:06 1999 PST
  </programlisting>
diff -cr cvs/pgsql/doc/src/sgml/datetime.sgml cvs.build/pgsql/doc/src/sgml/datetime.sgml
*** cvs/pgsql/doc/src/sgml/datetime.sgml	2006-05-15 22:59:37.000000000 +0200
--- cvs.build/pgsql/doc/src/sgml/datetime.sgml	2006-06-20 00:40:55.000000000 +0200
***************
*** 46,52 ****
         <para>
          If the numeric token contains a dash (<literal>-</>), slash
          (<literal>/</>), or two or more dots (<literal>.</>), this is
!         a date string which may have a text month.
         </para>
        </step>
  
--- 46,54 ----
         <para>
          If the numeric token contains a dash (<literal>-</>), slash
          (<literal>/</>), or two or more dots (<literal>.</>), this is
!         a date string which may have a text month. In case of a slash
!         (<literal>/</>) it can also be a full time zone name like
!         <literal>America/New_York</>.
         </para>
        </step>
  
***************
*** 359,365 ****
     </indexterm>
  
     <para>
!     <xref linkend="datetime-timezone-input-table"> shows the time zone
      abbreviations recognized by <productname>PostgreSQL</productname>
      in date/time input values.  Note that these names are <emphasis>not</>
      necessarily used for date/time output &mdash; output is driven by the
--- 361,368 ----
     </indexterm>
  
     <para>
!     <xref linkend="datetime-timezone-input-table"> and
!     <xref linkend="datetime-timezone-full-names-table"> show the time zone
      abbreviations recognized by <productname>PostgreSQL</productname>
      in date/time input values.  Note that these names are <emphasis>not</>
      necessarily used for date/time output &mdash; output is driven by the
***************
*** 983,995 ****
     </indexterm>
  
     <para>
!     <xref linkend="datetime-timezone-set-table"> shows the time zone
      names recognized by <productname>PostgreSQL</productname> as valid
      settings for the <xref linkend="guc-timezone"> parameter.  Note that
      these names are conceptually as well as practically different from
      the names shown in <xref linkend="datetime-timezone-input-table">:
      most of these names imply a local daylight-savings time rule, whereas
!     the former names each represent just a fixed offset from UTC.
     </para>
  
     <para>
--- 986,1000 ----
     </indexterm>
  
     <para>
!     <xref linkend="datetime-timezone-full-names-table"> shows the time zone
      names recognized by <productname>PostgreSQL</productname> as valid
      settings for the <xref linkend="guc-timezone"> parameter.  Note that
      these names are conceptually as well as practically different from
      the names shown in <xref linkend="datetime-timezone-input-table">:
      most of these names imply a local daylight-savings time rule, whereas
!     the former names each represent just a fixed offset from UTC. That's why
!     you always have to specify a date if you want to use these time zone
!     names in <type>timetz</> values.
     </para>
  
     <para>
***************
*** 998,1005 ****
      by the name of the principal city of the zone.
     </para>
  
!     <table id="datetime-timezone-set-table">
!      <title>Time Zone Names for Setting <varname>timezone</></title>
       <tgroup cols="1">
        <thead>
         <row>
--- 1003,1010 ----
      by the name of the principal city of the zone.
     </para>
  
!     <table id="datetime-timezone-full-names-table">
!      <title>Time Zone Names for date/time input values and for setting <varname>timezone</></title>
       <tgroup cols="1">
        <thead>
         <row>
diff -cr cvs/pgsql/doc/src/sgml/func.sgml cvs.build/pgsql/doc/src/sgml/func.sgml
*** cvs/pgsql/doc/src/sgml/func.sgml	2006-06-19 03:25:38.000000000 +0200
--- cvs.build/pgsql/doc/src/sgml/func.sgml	2006-06-19 14:48:41.000000000 +0200
***************
*** 6091,6097 ****
      specified either as a text string (e.g., <literal>'PST'</literal>)
      or as an interval (e.g., <literal>INTERVAL '-08:00'</literal>).
      In the text case, the available zone names are those shown in either
!     <xref linkend="datetime-timezone-set-table"> or
      <xref linkend="datetime-timezone-input-table">.
     </para>
  
--- 6091,6097 ----
      specified either as a text string (e.g., <literal>'PST'</literal>)
      or as an interval (e.g., <literal>INTERVAL '-08:00'</literal>).
      In the text case, the available zone names are those shown in either
!     <xref linkend="datetime-timezone-full-names-table"> or
      <xref linkend="datetime-timezone-input-table">.
     </para>