From: Ow Mun Heng <Ow.Mun.Heng@wdc.com>
To: Steinar H. Gunderson <sgunderson@bigfoot.com>
Cc: Carlo Stonebanks <stonec.register@sympatico.ca>
Cc: pgsql-performance@postgresql.org
Subject: Re: REPOST: Nested loops row estimates always too high
Date: Wed, 26 Sep 2007 11:50:46 +0800
Message-ID: <1190778646.5402.16.camel@neuromancer.home.net> (raw)
In-Reply-To: <20070925093133.GA27052@uio.no>
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>
<20070925093133.GA27052@uio.no>
On Tue, 2007-09-25 at 11:31 +0200, Steinar H. Gunderson wrote:
> 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 :-)
>
Where can I erad more about this new "feature"?
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: Ow.Mun.Heng@wdc.com, sgunderson@bigfoot.com, stonec.register@sympatico.ca
Subject: Re: REPOST: Nested loops row estimates always too high
In-Reply-To: <1190778646.5402.16.camel@neuromancer.home.net>
* 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