Re: Really dumb planner decision - Mailing list pgsql-performance

From Matthew Wakeling
Subject Re: Really dumb planner decision
Date
Msg-id alpine.DEB.2.00.0904161651420.4053@aragorn.flymine.org
Whole thread Raw
In response to Re: Really dumb planner decision  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Really dumb planner decision
List pgsql-performance
On Thu, 16 Apr 2009, Robert Haas wrote:
> I hasten to point out that I only suggested raising them to the moon
> as a DEBUGGING strategy, not a production configuration.

The problem is that we have created a view that by itself a very
time-consuming query to answer, relying on it being incorporated into a
query that will constrain it and cause it to be evaluated a lot quicker.
This kind of scenario kind of guarantees a bad plan as soon as the number
of tables reaches from_collapse_limit.

Matthew

--
 Failure is not an option. It comes bundled with your Microsoft product.
                                                 -- Ferenc Mantfeld

pgsql-performance by date:

Previous
From: Lists
Date:
Subject: Re: Shouldn't the planner have a higher cost for reverse index scans?
Next
From: Tom Lane
Date:
Subject: Re: Shouldn't the planner have a higher cost for reverse index scans?