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

From: "Michael A(dot) Olson" <mao(at)sleepycat(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Performance (was: The New Slashdot Setup (includes MySql server))
Date: 2000-05-19 16:54:11
Message-ID: 200005191656.JAA19183@triplerock.olsons.net
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.

mike

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kaare Rasmussen 2000-05-19 16:55:54 Re: The New Slashdot Setup (includes MySql server)
Previous Message Bruce Momjian 2000-05-19 16:54:10 Re: Performance (was: The New Slashdot Setup (includes MySql server))

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-05-19 16:55:01 CVS commit broken
Previous Message Bruce Momjian 2000-05-19 16:54:10 Re: Performance (was: The New Slashdot Setup (includes MySql server))