AT TIME ZONE bug in CVS?

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: AT TIME ZONE bug in CVS?
Date: 2002-08-21 08:41:50
Message-ID: GNELIHDDFBOCMGBFGEFOEENBCDAA.chriskl@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2002-08-21 08:59:47 CVS broken - large file support?
Previous Message Justin Clift 2002-08-21 08:30:18 Re: Multiple vulnerabilities in PostgreSQL