| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Magnus Hagander" <magnus(at)hagander(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 17:52:13 |
| Message-ID: | 87wswcld4i.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
"Andrew Dunstan" <andrew(at)dunslane(dot)net> writes:
> That's probably the worst of all possible options. Two very common uses of
> CSVlogs will be a) to load them into a PostgreSQL table and b) to load them into
> a spreadsheet such as Excel. In both cases having a Unix epoch time rather than
> a timestamp is likely to be very annoying.
Strangely those are precisely the use cases I was thinking of as well. For
both of those cases you need a timestamp which is unambiguous and understood
everywhere. Any text representation is going to depend on other tools using
the a compatible parser. Integers can be parsed by anything.
But perhaps I overestimate Excel's abilities.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Saito | 2007-08-03 17:53:42 | Re: Correction of how to use TimeZone by ControlFile(xlog.c) |
| Previous Message | Michael Glaesemann | 2007-08-03 17:51:31 | Re: Correction of how to use TimeZone by ControlFile(xlog.c) |