----- Original Message -----
From: "Tom Lane"
> keys remains reasonably static. The problem comes in if you have a
> range of values that keeps growing (eg, you are indexing a SERIAL or
> timestamp column). The right end of the btree keeps growing, but
> there's no mechanism to collapse out no-longer-used space at the left
> end.
>
related to this: it seems that there is no handy way to rebuild the index,
so that the it's storage is optimised (i.e. remove fragmentation).
Are there any plans for implementing ALTER INDEX ... REBUILD (or ALTER INDEX
... COALESCE) that could rebuild the index based only on its data, without
accessing the related table (which will be the case with DROP + CREATE for
the index)?
thanx,
Marin
----
"...what you brought from your past, is of no use in your present. When
you must choose a new path, do not bring old experiences with you.
Those who strike out afresh, but who attempt to retain a little of the
old life, end up torn apart by their own memories. "
