From: Michael Fuhr <mike@fuhr.org>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Functionscan estimates
Date: Fri, 8 Apr 2005 16:38:20 -0600
Message-ID: <20050408223820.GA17450@winnie.fuhr.org> (raw)
In-Reply-To: <200504081515.50340.josh@agliodbs.com>
References: <200504081515.50340.josh@agliodbs.com>
On Fri, Apr 08, 2005 at 03:15:50PM -0700, Josh Berkus wrote:
>
> I'm wondering if it might be useful to be able to add estimated selectivity to
> a function definition for purposes of query estimation. Currently function
> scans automatically return a flat default 1000 estimated rows. It seems
> like the DBA ought to be able to ALTER FUNCTION and give it a row estimate
> for planning purposes.
About a month ago I mentioned that I'd find that useful. In a
followup, Christopher Kings-Lynne brought up the idea of a GUC
variable that could give hints about the expected row count.
http://archives.postgresql.org/pgsql-hackers/2005-03/msg00146.phphttp://archives.postgresql.org/pgsql-hackers/2005-03/msg00153.php
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
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: mike@fuhr.org, josh@agliodbs.com
Subject: Re: Functionscan estimates
In-Reply-To: <20050408223820.GA17450@winnie.fuhr.org>
* 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