Re: [HACKERS] Re: partial index

From: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
To: Jan Wieck <jwieck(at)debis(dot)com>
Cc: "Jackson, DeJuan" <djackson(at)cpsgroup(dot)com>, maillist(at)candle(dot)pha(dot)pa(dot)us, aoki(at)CS(dot)Berkeley(dot)EDU, pgsql-hackers(at)hub(dot)org
Subject: Re: [HACKERS] Re: partial index
Date: 1998-08-13 01:43:40
Message-ID: 35D244CC.5AB4E6B3@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > > I had suspected that's what they were, but never really was sure. > > > Now the next question, "Should we rip them out?" No one uses
> > > them, and they seem to be of very limited usefulness.
> > > I am inclined to keep them, but I am not sure.
> > Do we have syntax for their creation and is it in the docs?
> > If not I say just take them out, unless someone can think of a use
> > that wouldn't be served by normal indexes.
> So the only argument for having a partial index can be saved
> disk space. A bad argument when looking at the actual pricing
> of disks.
> Don't force it - use a bigger hammer!
> Result: Kick the partial indices out.

???

Why remove another feature from Postgres when there isn't a clear
benefit to removing it? It's yet another discriminator separating
Postgres from ordinary database systems.

Now that we know what they are, we should figure out how to use them,
and document it as DeJuan suggests.

- Tom

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas G. Lockhart 1998-08-13 02:58:03 Re: [HACKERS] Re: type coersion (was OR clause status)
Previous Message Bruce Momjian 1998-08-12 20:07:54 Re: [HACKERS] Table permissions problem