Re: index / sequential scan problem

From: "Shridhar Daithankar" <shridhar_daithankar(at)persistent(dot)co(dot)in>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: index / sequential scan problem
Date: 2003-07-17 12:54:27
Message-ID: 3F16E9DB.15319.90FDAD@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 17 Jul 2003 at 14:50, Fabian Kreitner wrote:

> At 14:34 17.07.2003, you wrote:
> >I expect you will find that the third query is also a lot faster that the
> >first query.
>
> Im afraid, no.
> Database has been stopped / started right before this.
>
> perg_1097=# set enable_seqscan to true;
> SET VARIABLE
> perg_1097=# EXPLAIN ANALYZE select notiz_id, obj_id, obj_typ
> perg_1097-# from notiz_objekt a
> perg_1097-# where not exists

Well, he said query and not the query plan...:-)

While explain analyze is great for judging what is happening, it's not always a
good idea to trust the numbers produced by it. It will probably produce same
number for a SCSI disk machine and for a IDE disk machine, everything else
being equal. Obviously that is not correct.

Only thing you can trust in explain analyze is it's plan. Numbers are based on
heuristic and should be taken as hint only.

Bye
Shridhar

--
Harrisberger's Fourth Law of the Lab: Experience is directly proportional to
the amount of equipment ruined.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Jord Tanner 2003-07-17 14:10:35 Re: index / sequential scan problem
Previous Message Fabian Kreitner 2003-07-17 12:50:30 Re: index / sequential scan problem