Re: [HACKERS] Re: partial index - Mailing list pgsql-hackers

From Thomas G. Lockhart
Subject Re: [HACKERS] Re: partial index
Date
Msg-id 35D244CC.5AB4E6B3@alumni.caltech.edu
Whole thread Raw
In response to Re: [HACKERS] Re: partial index  (jwieck@debis.com (Jan Wieck))
List pgsql-hackers
> > > I had suspected that's what they were, but never really was sure.  > > > Now the next question, "Should we rip
themout?"   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

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Table permissions problem
Next
From: "Thomas G. Lockhart"
Date:
Subject: Re: [HACKERS] Re: type coersion (was OR clause status)