| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP: Fast GiST index build |
| Date: | 2011-07-13 08:33:17 |
| Message-ID: | 4E1D584D.2070706@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Looking at the performance test results again on the wiki page
(http://wiki.postgresql.org/wiki/Fast_GiST_index_build_GSoC_2011#Testing_results),
the patch can be summarized like this: it reduces the number of disk
accesses, at the cost of some extra CPU work.
Is it possible to switch to the new buffering method in the middle of an
index build? We could use the plain insertion method until the index
grows to a certain size (effective_cache_size?), and switch to the
buffering method after that.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Radosław Smogura | 2011-07-13 08:35:02 | Re: Patch Review: Bugfix for XPATH() if text or attribute nodes are selected |
| Previous Message | Christian Ullrich | 2011-07-13 08:22:50 | Re: isolation tests are not being run in buildfarm |