Re: Hints (Was: Index Tuning Features) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Hints (Was: Index Tuning Features)
Date
Msg-id 21792.1160701758@sss.pgh.pa.us
Whole thread Raw
In response to Re: Hints (Was: Index Tuning Features)  (Casey Duncan <casey@pandora.com>)
Responses Re: Hints (Was: Index Tuning Features)  ("Andrew Dunstan" <andrew@dunslane.net>)
Re: Hints (Was: Index Tuning Features)  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Casey Duncan <casey@pandora.com> writes:
> Yes, but it may be much more efficient for the human to tell the  
> computer than for the computer to introspect things. Take, for  
> example, ndisinct as data grows large.

Yeah, an override estimate for a column's ndistinct seems a perfect
example of the sort of statistical hint that I'd be in favor of having.
We have also talked about solving the multi-column statistics problem
(which, at its core, is "which combinations of columns are worth
accumulating stats for?" --- you can't possibly store stats for every
combination!) by having what would amount to hints from the DBA saying
"keep stats for these combinations".
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Andrew Dunstan"
Date:
Subject: Re: ./configure argument checking
Next
From: "Andrew Dunstan"
Date:
Subject: Re: Hints (Was: Index Tuning Features)