Re: An unresolved performance problem.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: An unresolved performance problem.
Date: 2003-05-08 14:42:55
Message-ID: 20336.1052404975@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-performance pgsql-sql

Andrew Sullivan <andrew(at)libertyrms(dot)info> writes:
> On Thu, May 08, 2003 at 10:48:52AM -0200, Achilleus Mantzios wrote:
>> That is, we have a marginal decrease of the total cost
>> for the index scan when random_page_cost = 1.9,
>> whereas the "real cost" in the means of total runtime
>> ranges from 218 msecs (seq scan) to 19 msecs (index scan).
>> (is it sane?)

> You're right that the problem is the poor estimate of the cost of
> that selection.

Are the table and index orders the same? Oliver Elphick pointed out
awhile ago that we're doing a bad job of index order correlation
estimation for multi-column indexes --- the correlation is taken to
be much lower than it should be. But if the correlation is near
zero anyway then this wouldn't explain Achilleus' problem...

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message johnnnnnn 2003-05-08 14:47:38 Re: [PERFORM] [SQL] Unanswered Questions WAS: An unresolved performance problem.
Previous Message Achilleus Mantzios 2003-05-08 12:48:52 Re: An unresolved performance problem.

Browse pgsql-performance by date

  From Date Subject
Next Message johnnnnnn 2003-05-08 14:47:38 Re: [PERFORM] [SQL] Unanswered Questions WAS: An unresolved performance problem.
Previous Message Achilleus Mantzios 2003-05-08 12:48:52 Re: An unresolved performance problem.

Browse pgsql-sql by date

  From Date Subject
Next Message johnnnnnn 2003-05-08 14:47:38 Re: [PERFORM] [SQL] Unanswered Questions WAS: An unresolved performance problem.
Previous Message Jon Earle 2003-05-08 14:18:03 Re: PostgreSQL Qs