From 0851a6fbc77e7f1762a2a94d370492f03450e922 Mon Sep 17 00:00:00 2001
From: Bruce Momjian
Date: Wed, 15 Jun 2005 00:34:11 +0000
Subject: This patch makes it possible to use the full set of timezones when
 doing "AT TIME ZONE", and not just the shorlist previously available. For
 example:

SELECT CURRENT_TIMESTAMP AT TIME ZONE 'Europe/London';

works fine now. It will also obey whatever DST rules were in effect at
just that date, which the previous implementation did not.

It also supports the AT TIME ZONE on the timetz datatype. The whole
handling of DST is a bit bogus there, so I chose to make it use whatever
DST rules are in effect at the time of executig the query. not sure if
anybody is actuallyi *using* timetz though, it seems pretty
unpredictable just because of this...

Magnus Hagander
---
 doc/src/sgml/datetime.sgml | 8 +++++---
 doc/src/sgml/func.sgml     | 7 ++-----
 2 files changed, 7 insertions(+), 8 deletions(-)

(limited to 'doc/src')

diff --git a/doc/src/sgml/datetime.sgml b/doc/src/sgml/datetime.sgml
index 0e42e34fd69..9610dc36c5c 100644
--- a/doc/src/sgml/datetime.sgml
+++ b/doc/src/sgml/datetime.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/datetime.sgml,v 2.45 2005/01/09 18:58:10 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/datetime.sgml,v 2.46 2005/06/15 00:34:08 momjian Exp $
 -->
 
  <appendix id="datetime-appendix">
@@ -990,7 +990,9 @@ $PostgreSQL: pgsql/doc/src/sgml/datetime.sgml,v 2.45 2005/01/09 18:58:10 tgl Exp
    <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
+    settings for the <xref linkend="guc-timezone"> parameter, and as
+	parameters to the <literal>AT TIME ZONE function</> (see 
+	<xref linkend="functions-datetime-zoneconvert">).  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
@@ -1004,7 +1006,7 @@ $PostgreSQL: pgsql/doc/src/sgml/datetime.sgml,v 2.45 2005/01/09 18:58:10 tgl Exp
    </para>
 
     <table id="datetime-timezone-set-table">
-     <title>Time Zone Names for Setting <varname>timezone</></title>
+     <title>Time Zone Names for Setting <varname>timezone</> and <literal>AT TIME ZONE</></title>
      <tgroup cols="1">
       <thead>
        <row>
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 4fe5e1d6fca..38e2c4a7001 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.256 2005/06/14 23:47:39 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.257 2005/06/15 00:34:08 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -5679,10 +5679,7 @@ SELECT date_trunc('year', TIMESTAMP '2001-02-16 20:38:40');
     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
-    <xref linkend="datetime-timezone-input-table">.  (It would be useful
-    to support the more general names shown in
-    <xref linkend="datetime-timezone-set-table">, but this is not yet
-    implemented.)
+    <xref linkend="datetime-timezone-set-table">.
    </para>
 
    <para>
-- 
cgit v1.2.3