Re: SeqScan costs

From: Decibel! <decibel(at)decibel(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Gregory Stark <stark(at)enterprisedb(dot)com>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SeqScan costs
Date: 2008-08-20 15:14:36
Message-ID: 0EF13902-9E3F-4FE1-BE12-A05116FF2644@decibel.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Aug 18, 2008, at 11:49 AM, Tom Lane wrote:
>> Perhaps what's also needed here is to measure just how accurate
>> the cpu_*
>> costs are. Perhaps they need to be raised somewhat if we're
>> underestimating
>> the cost of digging through 200 tuples on a heap page and the
>> benefit of a
>> binary search on the index tuples.
>
> Possibly. I doubt anyone's ever taken a hard look at the cpu_xxx
> values.

Josh Berkus indicated at PGCon that he's had luck *decreasing* the
CPU costs, but IIRC that was mostly on OLAP systems. It seems we need
some real data here.
--
Decibel!, aka Jim C. Nasby, Database Architect decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Sabino Mullane 2008-08-20 15:49:39 Re: A smaller default postgresql.conf
Previous Message Andrew Sullivan 2008-08-20 15:03:14 Re: Patch: plan invalidation vs stored procedures