On Wed, 24 Sep 2008, Sabin Coanda wrote:
> I think it would be nice to log the reasons why an explain analyze chooses a
> specific way or another for an execution plan. This would avoid wasting time
> to find the source of these decisions from the existing logs.
That would probably fill up the logs pretty quickly.
What may be really useful would be some sort of "extended explain" option.
At the moment, explain prints out the best query plan found. Sometimes it
would be nice if it printed out all the plans it considered, so we don't
have to go fiddling with enable_xxx to find alternatives.
I suppose some of you have done a Continuous Maths course. Yes? Continuous
Maths? <menacing stares from audience> Whoah, it was like that, was it!
-- Computer Science Lecturer
In response to
pgsql-performance by date
|Next:||From: Steve Clark||Date: 2008-09-24 11:11:57|
|Subject: Re: Intel's X25-M SSD|
|Previous:||From: Artis Caune||Date: 2008-09-24 10:52:44|
|Subject: Re: UFS 2: soft updates vs. gjournal (AKA: Choosing a filesystem 2.)|