Re: Macros for time magic values

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: "Dimitri Fontaine" <dimitri(at)2ndQuadrant(dot)fr>, "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:42:06
Message-ID: 25903.1300200126@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> 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.

Maybe, but if the docs started talking about that, we'd have to define
the term every time. The number of PG users who know what UT1 is can
probably be counted without running out of toes.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2011-03-15 14:44:57 Re: Patch to git_changelog for release note creation
Previous Message Tom Lane 2011-03-15 14:38:15 Re: Patch to git_changelog for release note creation