Re: Floating-point timestamps versus Range Types

Greg Stark wrote:
> On Thu, Oct 21, 2010 at 4:49 PM, Bruce Momjian <bruce@momjian.us> wrote:
> > One thing we have talked about is converting the page on read-in from
> > the backend. ?Since the timestamps are the same size as float or
> > integer, that might be possible.
> 
> Did we have a solution for the problem that understanding which
> columns are timestamps requires having a tuple descriptor and parsing
> the every tuple? That seems like it would a) be slow and b) require a
> lot of high level code in the middle of a low-level codepath.

Yep, that's what it requires.  It would rewrite in the new format.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +