From: | "Craig A(dot) James" <cjames(at)modgraph-usa(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Overriding the optimizer |
Date: | 2005-12-16 03:11:53 |
Message-ID: | 43A23079.8060307@modgraph-usa.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Christopher Kings-Lynne wrote:
> Can you paste explain analyze and your effective_cache_size, etc. settings.
> ...
> This seems like a case where PostgreSQL's current optimiser should
> easily know what to do if your config settings are correct and you've
> been running ANALYZE, so I'd like to see your settings and the explain
> analyze plan...
I could, but it would divert us from the main topic of this discussion. It's not about that query, which was just an example. It's the larger issue.
Tom's earlier response tells the story better than I can:
> This discussion has been had before (many times) ... see
> the -hackers archives for detailed arguments.
If it's "been had before (many times)", and now I'm bringing it up again, then it's clearly an ongoing problem that hasn't been resolved.
Craig
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Kirkwood | 2005-12-16 03:16:58 | Re: Overriding the optimizer |
Previous Message | Craig A. James | 2005-12-16 03:04:03 | Re: Overriding the optimizer |