| From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jaime Casanova <systemguards(at)gmail(dot)com>, "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: Maintaining cluster order on insert |
| Date: | 2007-07-10 11:43:06 |
| Message-ID: | 469370CA.1060608@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Gregory Stark wrote:
> It's pretty serious what you're suggesting since it means that we'll basically
> never have a real cluster feature. I would sure hope we're missing something
> and there's a way to make this work usefully.
Another approach would be an online CLUSTER command. That means there'll
be a lot of churn when tuples need to be moved back and forth, along
with updating indexes, but it'd take the overhead out of the critical path.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karsten Hilbert | 2007-07-10 12:14:30 | Re: russian case-insensitive regexp search not working |
| Previous Message | Gregory Stark | 2007-07-10 11:23:23 | Re: Maintaining cluster order on insert |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2007-07-10 12:52:54 | Re: Maintaining cluster order on insert |
| Previous Message | Gregory Stark | 2007-07-10 11:23:23 | Re: Maintaining cluster order on insert |