From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Magnus Hagander" <magnus(at)hagander(dot)net>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp>, <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Correction of how to use TimeZone by ControlFile(xlog.c) |
Date: | 2007-08-03 15:18:47 |
Message-ID: | 874pjgbq94.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Gregory Stark <stark(at)enterprisedb(dot)com> writes:
>> "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>>> I don't think it's an acceptable change in either place. People who
>>> want to see UTC in their logs can start the postmaster in UTC. Those
>>> who are accustomed to seeing local time will squawk.
>
>> It would probably make sense to use UTC in the CSV logs since they're intended
>> to be machine readable. Whatever program is used to read them can handle
>> displaying the timestamps in the appropriate timezone for user's consumption.
>
> I don't think we really want to pay for formatting the timestamp twice
> (the existing patch goes out of its way to avoid that IIRC).
Well even if we include the time in integer seconds-since-unix-epoch format it
would be useful for a CSV data format.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Saito | 2007-08-03 15:25:28 | Re: Correction of how to use TimeZone by ControlFile(xlog.c) |
Previous Message | Tom Lane | 2007-08-03 14:44:08 | Re: Correction of how to use TimeZone by ControlFile(xlog.c) |