Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Poor performance o
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Craig A. James" <cjames(at)modgraph-usa(dot)com>
- Cc: pgsql-performance(at)postgresql(dot)org
- Subject: Re: Poor performance o
- Date: Tue, 21 Mar 2006 18:33:15 -0500
"Craig A. James" <cjames(at)modgraph-usa(dot)com> writes: > It looks to me like the problem is the use of nested loops when a hash join should be used, but I'm no expert at query planning. Given the sizes of the tables involved, you'd likely have to boost up work_mem before the planner would consider a hash join. What nondefault configuration settings do you have, anyway? regards, tom lane
- Follow-Ups:
- Re: Poor performance o
- From: Craig A. James
- Re: Poor performance o
- References:
- Re: qsort again (was Re: Strange Create Index behaviour)
- From: Tom Lane
- Poor performance o
- From: Craig A. James
- Re: qsort again (was Re: Strange Create Index behaviour)
- Prev by Date: Poor performance o
- Next by Date: Re: Poor performance o
- Previous by thread: Poor performance o
- Next by thread: Re: Poor performance o
- Indexes: