On Wed, 2008-04-23 at 19:43 -0700, Ron Mayer wrote:
> Tom Lane wrote:
> > Simon Riggs <simon@2ndquadrant.com> writes:
> >> On Wed, 2008-04-23 at 12:07 -0400, Tom Lane wrote:
> >>> To be acceptable, a GIT patch would have to be optional and it
> >>> ...
> > I was considering a new pg_index column. Or else we'd have to fix
> > the storage-parameter infrastructure to support restricting changes
> > of some parameters.
>
>
> Interesting. Does this mean that down the road a postgis index
> might be GIT-ified?
Yes, all types of index can benefit from some form of compression. The
only issue is that there isn't one technique that covers all use cases,
so it will take time and we should be careful to do the most important
ones first.
> On my biggest tables (clustered by zip/postal code) the index on
> the geometry column with a postgis index probably sees all the
> rows on each of it's pages pointing to the same few heap pages.
> If I understand right, that's the kind of pattern that GIT helps.
-- Simon Riggs 2ndQuadrant http://www.2ndQuadrant.com
