Skip site navigation (1) Skip section navigation (2)

Re: code cleanup of timestamp code

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Warren Turkal <turkal(at)google(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: code cleanup of timestamp code
Date: 2008-02-26 09:37:07
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Tue, Feb 26, 2008 at 12:22:03AM -0800, Warren Turkal wrote:
> As a result, I have a few questions about the timestamp code. In what
> instances is the floating point timestamp recommended? I see that
> Debian and Ubuntu ship packages that use the int64 timestamps. Is the
> backend smart enough to not load and use a database with timestamp
> fields created with the representation not compiled into the compiler?
> And finally, would this work be welcome in PostgreSQL? I view is as a
> kind of beginner janitor type of project to get my feet wet.

AIUI it's because there are systems that have broken 64-integer
support. Or at least, that's the theory. There was a question recently
to check if there really are such systems still running...

Have a nice day,
Martijn van Oosterhout   <kleptog(at)svana(dot)org>
> Those who make peaceful revolution impossible will make violent revolution inevitable.
>  -- John F Kennedy

In response to

pgsql-hackers by date

Next:From: Peter EisentrautDate: 2008-02-26 10:22:58
Subject: Re: [COMMITTERS] pgsql: Link postgres from all object files at once, to avoid the
Previous:From: Magnus HaganderDate: 2008-02-26 09:26:04
Subject: Re: libpq.rc make rule

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group