From: | "Aleksis Petrov" <a(dot)aleksis(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | TODO item: Improve speed with indexes |
Date: | 2007-03-16 21:10:52 |
Message-ID: | bd9c4fd00703161410x3ad557a4i8aa994bdb0144fe3@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi everyone,
Regarding the mentioned TODO item, the past discussion as I see from the
following thread:
http://archives.postgresql.org/pgsql-general/2007-01/msg00879.php
concludes that during vacuum full, the relations' indexes should be
recreated via REINDEX, rather than updating them.
One solution which I see to this is to simply invoke reindex_relation(), or
the lower level reindex_index() function somewhere after full_vacuum_rel()
routine is done with its work.
I prototyped this and it does solve the problem of index bloating during
vacuum full. However this may not be the best solution since full_vacuum_rel
function is still updating the relation's indexes.
The other solution could be to not update the indexes at all (just REINDEX
it). But this does'nt seem to fit in with the current implementation of
repair_frag() function.
What do you all think would be the correct approach to solve this?
Thanks
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2007-03-16 21:12:33 | Re: [PATCHES] Bitmapscan changes |
Previous Message | Alvaro Herrera | 2007-03-16 20:59:18 | Re: Question: pg_class attributes and race conditions ? |