Skip site navigation (1) Skip section navigation (2)

Re: severe performance issue with planner

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Eric Brown" <bigwhitecow(at)hotmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: severe performance issue with planner
Date: 2004-03-28 17:16:18
Message-ID: 16579.1080494178@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
"Eric Brown" <bigwhitecow(at)hotmail(dot)com> writes:
> Here's the query as I have changed it now:

Now that you've switched to JOIN syntax, you can cut the planning time
to nil by setting join_collapse_limit to 1.  See
http://www.postgresql.org/docs/7.4/static/explicit-joins.html

			regards, tom lane

In response to

pgsql-performance by date

Next:From: Josh BerkusDate: 2004-03-28 19:24:43
Subject: Re: postgres eating CPU on HP9000
Previous:From: Marcus Andree S. MagalhaesDate: 2004-03-27 10:38:37
Subject: Re: postgres eating CPU on HP9000

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group