Re: optimizer parameters

From: Greg Smith <greg(at)2ndQuadrant(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: optimizer parameters
Date: 2011-04-11 02:40:48
Message-ID: 4DA26A30.6010208@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 04/10/2011 07:27 PM, Tomas Vondra wrote:
> But if you need more details, then I quess the best approach to get it
> is to read the sources (search for the cost estimation etc.).
>

There's a small fully worked out example of this in my book too, where I
duplicate the optimizer's EXPLAIN cost computations for a simple query.
The main subtle thing most people don't appreciate fully is how much the
optimizer takes into account two things: the selectivity of operators,
and the expected size of the data being moved around. For example, a
lot of the confusion around "why didn't it use my index?" comes from not
noticing the size of the index involved, and therefore how expensive its
page cost is considered to be.

--
Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
"PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Scott Marlowe 2011-04-11 05:35:49 Re: Multiple index builds on same table - in one sweep?
Previous Message Greg Smith 2011-04-11 02:29:49 Re: Multiple index builds on same table - in one sweep?