| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | silly sad <sad(at)bestmx(dot)ru> |
| Cc: | pgsql-advocacy <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | Re: Top five challenges |
| Date: | 2011-03-01 13:15:46 |
| Message-ID: | 1298985252-sup-744@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-www |
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?
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2011-03-02 00:36:36 | Re: Top five challenges |
| Previous Message | Florian Weimer | 2011-03-01 11:46:26 | Re: Top five challenges |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2011-03-01 17:17:30 | Re: .oO - Translation |
| Previous Message | Florian Weimer | 2011-03-01 11:46:26 | Re: Top five challenges |