On Apr 30, 2011, at 7:38 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>> Actually we had to solve a issue with slow SELECT. The problem was in
>> low value of JOIN_COLLAPSE_LIMITS. Can we increase a default of this
>> value. I checked some complex query, and planner needed about 200ms
>> for JOIN_COLLAPSE_LIMIT = 16. So some around 12 can be well.
> 
> I'd like to see a rather larger survey of cases before changing that.
> Also, amount of memory consumed is at least as large a concern here
> as runtime.

I seem to remember that I was the last one to suggest raising these limits and someone demonstrated rather convincingly that for certain classes of queries that would cause really big problems.

...Robert

In response to

• Re: increasing collapse_limits? at 2011-04-30 17:38:38 from Tom Lane

Responses

• Re: increasing collapse_limits? at 2011-04-30 20:21:54 from Tom Lane

pgsql-hackers by date

Next:	From: Dimitri Fontaine	Date: 2011-04-30 19:56:48
	Subject: Re: [HACKERS] PostgreSQL Core Team
Previous:	From: Robert Haas	Date: 2011-04-30 19:34:09
	Subject: Re: CLUSTER vs toast vacuuming: there's still a problem