| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| 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-21 23:55:01 |
| Message-ID: | AANLkTik8L2iOqm-cZCgbYLW9fsXjPG=5okByFtui2X9q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-10-22 00:00:46 | Re: Creation of temporary tables on read-only standby servers |
| Previous Message | Bruce Momjian | 2010-10-21 23:49:54 | Re: Floating-point timestamps versus Range Types |