Re: Really dumb planner decision

From: Matthew Wakeling
Subject: Re: Really dumb planner decision
Date: ,
Msg-id: alpine.DEB.2.00.0904161259590.4053@aragorn.flymine.org
(view: Whole thread, Raw)
In response to: Re: Really dumb planner decision  (Robert Haas)
Responses: Re: Really dumb planner decision  (Merlin Moncure)
List: pgsql-performance

Tree view

Really dumb planner decision  (Matthew Wakeling, )
 Re: Really dumb planner decision  (Grzegorz Jaśkiewicz, )
  Re: Really dumb planner decision  (Matthew Wakeling, )
   Re: Really dumb planner decision  (Robert Haas, )
    Re: Really dumb planner decision  (Matthew Wakeling, )
     Re: Really dumb planner decision  (Merlin Moncure, )
      Re: Really dumb planner decision  (Tom Lane, )
       Re: Really dumb planner decision  ("Kevin Grittner", )
        Re: Really dumb planner decision  (Merlin Moncure, )
       Re: Really dumb planner decision  (Robert Haas, )
        Re: Really dumb planner decision  (Matthew Wakeling, )
         Re: Really dumb planner decision  (Tom Lane, )
 Re: Really dumb planner decision  (Grzegorz Jaśkiewicz, )
  Re: Really dumb planner decision  (Matthew Wakeling, )

On Thu, 16 Apr 2009, Robert Haas wrote:
> What happens if you change join_collapse_limit and from_collapse_limit
> to some huge number?
>
> http://www.postgresql.org/docs/current/static/runtime-config-query.html#GUC-FROM-COLLAPSE-LIMIT

That solves the problem. So, a view is treated as a subquery then?

Matthew

--
 Contrary to popular belief, Unix is user friendly. It just happens to be
 very selective about who its friends are.                 -- Kyle Hearn


pgsql-performance by date:

From: Tom Lane
Date:
Subject: Re: GiST index performance
From: Matthew Wakeling
Date:
Subject: Re: GiST index performance