| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Dimitri Fontaine" <dimitri(at)2ndQuadrant(dot)fr>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Simon Riggs" <simon(at)2ndQuadrant(dot)com>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Macros for time magic values |
| Date: | 2011-03-15 14:36:15 |
| Message-ID: | 4D7F330F020000250003B8BC@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> writes:
>> Would it help moving toward Leap Second support, and is this
>> something we want to have?
>
> IMO we don't want to have that, as it would completely bollix
> datetime calculations of all kinds. You couldn't even count on
> stored timestamps not changing their meaning.
I'm inclined to agree, but if that's the choice, should we stop
claiming that we're using UTC, and instead claim UT1 support? It
always seemed a little odd to me that the docs say UTC but there's
no actual support for leap seconds in calculations.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-03-15 14:36:20 | Re: Patch to git_changelog for release note creation |
| Previous Message | Bruce Momjian | 2011-03-15 14:33:23 | Re: Patch to git_changelog for release note creation |