pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Steinar H. Gunderson <sgunderson@bigfoot.com>
To: Carlo Stonebanks <stonec.register@sympatico.ca>
Cc: Ow Mun Heng <Ow.Mun.Heng@wdc.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: REPOST: Nested loops row estimates always too high
Date: Tue, 25 Sep 2007 11:31:33 +0200
Message-ID: <20070925093133.GA27052@uio.no> (raw)
In-Reply-To: <53877A06E07146D2898619A7025C6107@serenity>
References: <fcu215$2em3$1@news.hub.org>
	<1190616376.17050.51.camel@neuromancer.home.net>
	<fd8ukj$s38$1@news.hub.org>
	<1190681440.22945.8.camel@neuromancer.home.net>
	<53877A06E07146D2898619A7025C6107@serenity>

On Tue, Sep 25, 2007 at 12:53:55AM -0400, Carlo Stonebanks wrote:
> My problem is that I think that SRF's are causing my problems. The SRF's
> gets an automatic row estimate of 1000 rows. Add a condition to it, the
> planner guesses 333 rows. Even at 333, this is an overestimate of the number
> of rows returned.
> 
> I'm really disappointed - SRF's are a great way to place the enterprise's
> db-centric business logic at the server.

Fortunately, in 8.3 you can attach a row estimate to the function yourself,
which should most likely fix your problem. Look forward to the first beta :-)

/* Steinar */
-- 
Homepage: http://www.sesse.net/



view thread (10+ messages)  latest in thread

Message-ID: <20070925093133.GA27052@uio.no>
Permalink:  ../20070925093133.GA27052@uio.no/
Also on:    postgresql.org/message-id/20070925093133.GA27052@uio.no

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: sgunderson@bigfoot.com, stonec.register@sympatico.ca, Ow.Mun.Heng@wdc.com
  Subject: Re: REPOST: Nested loops row estimates always too high
  In-Reply-To: <20070925093133.GA27052@uio.no>

* 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