AT TIME ZONE bug in CVS? - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject AT TIME ZONE bug in CVS?
Date
Msg-id GNELIHDDFBOCMGBFGEFOEENBCDAA.chriskl@familyhealth.com.au
Whole thread Raw
List pgsql-hackers
What's with this?

template1=# select current_timestamp(0);     timestamptz
------------------------2002-08-21 16:39:40+08
(1 row)

template1=# set time zone 'Australia/Sydney';
SET
template1=# select current_timestamp(0);     timestamptz
------------------------2002-08-21 18:39:49+10
(1 row)

template1=# select current_timestamp(0) at time zone 'Australia/Sydney';
ERROR:  Time zone 'australia/sydney' not recognized
template1=# select current_timestamp(0) at time zone 'AEST';     timezone
---------------------2002-08-21 18:40:07
(1 row)

Shouldn't the textual version of the time zone work using 'at time zone' as
well as 'set time zone'?

And also, why does the column name change from timestamptz to timezone?
Anyway, shouldn't it in fact be current_timestamp?

Chris



pgsql-hackers by date:

Previous
From: Justin Clift
Date:
Subject: Re: Multiple vulnerabilities in PostgreSQL
Next
From: "Christopher Kings-Lynne"
Date:
Subject: CVS broken - large file support?