Re: [GENERAL] now() AT TIME ZONE 'GMT';

From: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Richard Emberson <emberson(at)phc(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [GENERAL] now() AT TIME ZONE 'GMT';
Date: 2002-04-09 06:22:53
Message-ID: 3CB288BD.DEBCD0B6@fourpalms.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

(on -hackers)

> If you apply the AT TIME ZONE operator to a TIMESTAMP WITH TIME ZONE
> value, what happens is the internal GMT value is rotated to the
> specified zone and then the output is labeled as type TIMESTAMP WITHOUT
> TIME ZONE, preventing any further automatic zone rotations.

Hmm. That is how it probably *should* work, but at the moment the
timestamptz_zone() function actually outputs a character string! That is
a holdover from previous versions which did not have a "no zone"
timestamp; it would seem now to be more appropriate to output a no-zone
timestamp.

I'll look at changing this in my upcoming patch set...

- Thomas

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jean-Michel POURE 2002-04-09 06:32:23 Re: Porting from MySql - meta data issues
Previous Message Ed Loehr 2002-04-09 05:36:51 Re: Hash Join vs Nested Loops in 7.2.1 ...

Browse pgsql-hackers by date

  From Date Subject
Next Message Karel Zak 2002-04-09 07:54:56 Re: timeout implementation issues
Previous Message Joe Conway 2002-04-09 05:57:47 Re: unknownin/out patch (was [HACKERS] PQescapeBytea is