| From: | Alvaro Herrera Munoz <alvherre(at)dcc(dot)uchile(dot)cl> |
|---|---|
| To: | Hannu Krosing <hannu(at)tm(dot)ee> |
| Cc: | James Rogers <jamesr(at)best(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Index/Function organized table layout |
| Date: | 2003-10-02 21:08:21 |
| Message-ID: | 20031002210821.GA13592@dcc.uchile.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 02, 2003 at 10:09:12PM +0300, Hannu Krosing wrote:
> So what you really need is the CLUSTER command to leave pages half-empty
> and the tuple placement logic on inserts/updates to place new tuples
> near the place where they would be placed by CLUSTER. I.e. the code that
> does actual inserting should be aware of CLUSTERing.
Oh, you mean like what I half-proposed in
http://archives.postgresql.org/pgsql-general/2002-06/msg00968.php
BTW, this is the one message (the one on the CVS log I cite at the end)
that got me into Postgres hacking. The little involvement I've had has
been great. Thanks to all PostgreSQL hackers!
--
Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
"El realista sabe lo que quiere; el idealista quiere lo que sabe" (Anonimo)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Database | 2003-10-02 21:10:42 | US-CA DATABASE INTERNALS |
| Previous Message | James Rogers | 2003-10-02 20:44:51 | Re: Index/Function organized table layout |