| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jaime Casanova" <systemguards(at)gmail(dot)com>, "PostgreSQL-patches" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: Maintaining cluster order on insert |
| Date: | 2007-06-18 08:49:28 |
| Message-ID: | 87wsy1hckn.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
"Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> writes:
> The reason for switching to the new API instead of the amsuggestblock API is
> CPU overhead. It avoids constructing the IndexTuple twice and descending the
> tree twice.
I wonder if it's possible to finesse this. Have the suggestblock function
remember the last block it suggested and somehow recognize when it's given the
same tuple to index. Keeping the block pinned would still be the sticky point
though.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-06-18 08:53:28 | Re: EXPLAIN omits schema? |
| Previous Message | Simon Riggs | 2007-06-18 08:42:25 | Re: Load Distributed Checkpoints test results |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-06-18 09:02:21 | Remove comment about tab-complete.c |
| Previous Message | Heikki Linnakangas | 2007-06-18 05:52:55 | Re: Maintaining cluster order on insert |