Re: AT TIME ZONE bug in CVS?

From: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: AT TIME ZONE bug in CVS?
Date: 2002-08-21 15:59:44
Message-ID: 3D63B8F0.5C71B50A@fourpalms.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> template1=# select current_timestamp(0) at time zone 'Australia/Sydney';
> ERROR: Time zone 'australia/sydney' not recognized

The input is done using an internal lookup, not your system's time zone
database. Much faster; setting time zone variables for every input will
be substantially slower (though I haven't measured how much, it will
involve opening files etc etc).

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

The feature is implemented as a function call to timezone(), which
returns a string. If it stayed a timestamp or something like that the
time zone can not be "frozen" through the formatting/output process.

- Thomas

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas SB SD 2002-08-21 16:10:48 Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in
Previous Message Robert Treat 2002-08-21 15:43:20 Re: @(#)Mordred Labs advisory 0x0003: Buffer overflow in