Re: Performance (was: The New Slashdot Setup (includes MySql server))

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: "Michael A(dot) Olson" <mao(at)sleepycat(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Performance (was: The New Slashdot Setup (includes MySql server))
Date: 2000-05-19 17:14:30
Message-ID: 200005191714.NAA07668@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

> At 12:39 PM 5/19/00 -0400, Tom Lane wrote:
>
> > Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2000-05-19 17:17:32 Auto-uppercase inserted column
Previous Message Ross J. Reedstrom 2000-05-19 17:05:26 Re: OO Patch

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-05-19 17:36:29 Re: Performance (was: The New Slashdot Setup (includes MySql server))
Previous Message Ross J. Reedstrom 2000-05-19 17:05:26 Re: OO Patch