Re: Shouldn't we have a way to avoid "risky" plans? - Mailing list pgsql-performance

From Justin Pitts
Subject Re: Shouldn't we have a way to avoid "risky" plans?
Date
Msg-id AANLkTikeS8ChvSydcMXhLbz8t4AUUx+iUFTinANwHtfX@mail.gmail.com
Whole thread Raw
In response to Shouldn't we have a way to avoid "risky" plans?  (Josh Berkus <josh@agliodbs.com>)
List pgsql-performance
On Wed, Mar 23, 2011 at 1:12 PM, Josh Berkus <josh@agliodbs.com> wrote:
> AFAICT, what's happening in this query is that PostgreSQL's statistics
> on the device_nodes and several other tables are slightly out of date
> (as in 5% of the table).

What about some manner of query feedback mechanism ( along the lines
of what explain analyze yields ) to track "stats staleness" in
general?

Probably, I misunderstand the costs of executing explain analyze.

pgsql-performance by date:

Previous
From: Claudio Freire
Date:
Subject: Re: Shouldn't we have a way to avoid "risky" plans?
Next
From: Tom Lane
Date:
Subject: Re: Shouldn't we have a way to avoid "risky" plans?