> At 12:39 PM 5/19/00 -0400, Tom Lane wrote:
>
> > Bruce Momjian <pgman@candle.pha.pa.us> writes:
> >
> > > We have indexes on all system tables that need it.
> >
> > There isn't any fundamental reason why the planner can't be using an
> > index to scan pg_index; we just need to code it that way. Right now
> > it's coded as a sequential scan.
>
> Eliminating the hard-coded seqscans of catalogs in the bowels of the
> system was the hardest part of the project. As I said, it was good
> to do. It made parsing and planning queries much, much faster.
All the sequential catalog scans that return one row are gone. What has
not been done is adding indexes for scans returning more than one row.
-- Bruce Momjian | http://www.op.net/~candle pgman@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026
