Skip site navigation (1) Skip section navigation (2)

Re: Top five challenges

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: sad <sad(at)bestmx(dot)ru>
Cc: pgsql-advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: Top five challenges
Date: 2011-03-02 14:08:06
Message-ID: 1299074862-sup-9983@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-advocacypgsql-www
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(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

pgsql-www by date

Next:From: Grant SlaterDate: 2011-03-02 16:25:23
Subject: Re: Top five challenges
Previous:From: Alvaro HerreraDate: 2011-03-02 14:07:28
Subject: Re: Top five challenges

pgsql-advocacy by date

Next:From: Grant SlaterDate: 2011-03-02 16:25:23
Subject: Re: Top five challenges
Previous:From: Alvaro HerreraDate: 2011-03-02 14:07:28
Subject: Re: Top five challenges

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group