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

From Christopher Kings-Lynne
Subject Re: Manual vs automatic functionality
Date
Msg-id 422A787F.7060306@familyhealth.com.au
Whole thread Raw
In response to Re: Manual vs automatic functionality  (Michael Fuhr <mike@fuhr.org>)
List pgsql-hackers
> 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.

Hmmm, you could jank that by making a new GUC:

SET expected_srf_rows TO 152;
SELECT * FROM myfunction();

Chris


pgsql-hackers by date:

Previous
From: Vikram Kalsi
Date:
Subject: Re: postgreSQL-8.0.1 compilation with icc-8.1 on Itanium-2 gives "error: asm statements not supported"
Next
From: Tom Lane
Date:
Subject: Cost of XLogInsert CRC calculations