From: | sad(at)bestmx(dot)ru |
---|---|
To: | pgsql-advocacy <pgsql-advocacy(at)postgresql(dot)org> |
Subject: | Re: Top five challenges |
Date: | 2011-03-02 13:35:59 |
Message-ID: | Prayer.1.3.3.1103021435590.25961@km21038-04.keymachine.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-www |
On Mar 1 2011, Alvaro Herrera wrote:
>Excerpts from silly sad's message of mar mar 01 03:39:35 -0300 2011:
>
>> 3. To make TIMESTAMPTZ useful by introducing proper type cast
>> TIMESTAMPTZ to TIMESTAMP
>
>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)
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2011-03-02 14:07:28 | Re: Top five challenges |
Previous Message | sad | 2011-03-02 13:23:53 | Re: Top five challenges |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2011-03-02 14:07:28 | Re: Top five challenges |
Previous Message | sad | 2011-03-02 13:23:53 | Re: Top five challenges |