Re: Manual vs automatic functionality - Mailing list pgsql-hackers

From Michael Fuhr
Subject Re: Manual vs automatic functionality
Date
Msg-id 20050305170526.GA70196@winnie.fuhr.org
Whole thread Raw
In response to Manual vs automatic functionality  (pgsql@mohawksoft.com)
Responses Re: Manual vs automatic functionality  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
List pgsql-hackers
On Sat, Mar 05, 2005 at 11:05:32AM -0500, pgsql@mohawksoft.com wrote:

> Being able to assign "hints" to queries may be able to allow DBAs to tune
> queries in tables who's characteristics are misrepresented by the
> statistics in ANALYZE.

I wouldn't mind being able to provide hints to the planner.  For
example, I have some set-returning functions that typically return
10-100 rows and I usually have a good idea of how many rows a
particular set of inputs will generate, and sometimes I know other
characteristics about those rows as well.  But the planner, not
knowing any better, always assumes the functions will return 1000
rows, which presumably affects the plan, sometimes for the worse.
Here's an example of a problem I've had:

http://archives.postgresql.org/pgsql-performance/2004-08/msg00236.php

I've wondered if the ability to provide hints about the expected
output from set-returning functions would be useful.

-- 
Michael Fuhr
http://www.fuhr.org/~mfuhr/


pgsql-hackers by date:

Previous
From: pgsql@mohawksoft.com
Date:
Subject: Manual vs automatic functionality
Next
From: "Alex"
Date:
Subject: Explicit Transaction Priority