| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Floating-point timestamps versus Range Types |
| Date: | 2010-10-22 01:29:06 |
| Message-ID: | 201010220129.o9M1T6G10117@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greg Stark wrote:
> On Thu, Oct 21, 2010 at 4:49 PM, Bruce Momjian <bruce(at)momjian(dot)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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-10-22 01:52:40 | Re: Simplifying replication |
| Previous Message | Josh Berkus | 2010-10-22 01:09:57 | Re: Simplifying replication |