pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Manfred Koizar <mkoi-pg@aon.at>
Cc: Jenny Zhang <jenny@osdl.org>
Cc: perf-pgsql <pgsql-performance@postgresql.org>
Cc: Matt Clark <matt@ymogen.net>
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] osdl-dbt3 run results - puzzled by the execution
Date: Wed, 24 Sep 2003 10:01:09 -0400
Message-ID: <3530.1064412069@sss.pgh.pa.us> (raw)
In-Reply-To: <4sj2nvcla6v5v9e3cr96kopjtda7k6mq8v@email.aon.at>
References: <1063924610.31150.75.camel@ibm-a.pdx.osdl.net>
	<3c6mmvcmvlr59kng6tnee2a0q4vf4spctt@email.aon.at>
	<1063996535.32392.9.camel@ibm-a.pdx.osdl.net>
	<4sj2nvcla6v5v9e3cr96kopjtda7k6mq8v@email.aon.at>

Manfred Koizar <mkoi-pg@aon.at> writes:
> Cutting down the number of heap page fetches if PF1 * L > P and P <
> effective_cache_size seems like an obvious improvement, but I was not
> able to figure out where to make this change.  Maybe it belongs into
> costsize.c near
> 	run_cost += outer_path_rows *
> 		(inner_path->total_cost - inner_path->startup_cost) *
> 		joininfactor;

I've been intending for some time to try to restructure the cost
estimator so that repeated indexscans can be costed more accurately.
Within the context of the heap-fetch-estimating algorithm, I think
the entire execution of a nestloop-with-inner-index-scan could probably
be treated as a single scan.  I'm not sure how we adjust the estimates
for the index-access part, though clearly those are too high as well.

This doesn't seem to be a localized change unfortunately.  Certainly
costsize.c can't do it alone.

			regards, tom lane



view thread (12+ messages)

Message-ID: <3530.1064412069@sss.pgh.pa.us>
Permalink:  ../3530.1064412069@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3530.1064412069@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, mkoi-pg@aon.at, jenny@osdl.org, matt@ymogen.net, pgsql-hackers@postgresql.org
  Subject: Re: [HACKERS] osdl-dbt3 run results - puzzled by the execution
  In-Reply-To: <3530.1064412069@sss.pgh.pa.us>
  References: <1063924610.31150.75.camel@ibm-a.pdx.osdl.net> <3c6mmvcmvlr59kng6tnee2a0q4vf4spctt@email.aon.at> <1063996535.32392.9.camel@ibm-a.pdx.osdl.net> <4sj2nvcla6v5v9e3cr96kopjtda7k6mq8v@email.aon.at> <3530.1064412069@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox