Re: Top five challenges - Mailing list pgsql-advocacy

From Alvaro Herrera
Subject Re: Top five challenges
Date
Msg-id 1299074862-sup-9983@alvh.no-ip.org
Whole thread Raw
In response to Re: Top five challenges  (sad@bestmx.ru)
List pgsql-advocacy
Excerpts from sad's message of mié mar 02 10:35:59 -0300 2011:
> On Mar 1 2011, Alvaro Herrera wrote:
>
> >Excerpts from silly sad's message of mar mar 01 03:39:35 -0300 2011:

> >I think this is the AT TIME ZONE operator (works both ways).
> >
> >> 4. Introduce a pair of preferences (server_timezone, client_timezone)
> >> instead of a single pref (timezone) (and use their values similar as
> >> (client_encoding, server_encoding) are used)
> >
> >I think server_timezone is hardwired as GMT.  client_timezone is our
> >current timezone setting.  I don't see the point in having
> >server_timezone be configurable ... is there one?
>
> GMT? let it be.
> i only ask u to USE IT while casting ::TIMESTAMPTZ::TIMESTAMP
> (instead of dropping TZ information)

As I said in my previous response, don't cast.  Use AT TIME ZONE.

--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-advocacy by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Top five challenges
Next
From: Grant Slater
Date:
Subject: Re: Top five challenges