Re: performance with query

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Alberto Dalmaso" <dalmaso(at)clesius(dot)it>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: performance with query
Date: 2009-06-16 15:32:36
Message-ID: 4A3774C40200002500027BED@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Alberto Dalmaso <dalmaso(at)clesius(dot)it> wrote:
> Il giorno mar, 16/06/2009 alle 15.58 +0100, Matthew Wakeling ha
> scritto:
>> On Tue, 16 Jun 2009, Alberto Dalmaso wrote:

>> > enable_hashjoin = off
>> > enable_nestloop = off
>> > enable_seqscan = off
>> > enable_sort = off
>>
>> Why are these switched off?
>>
> because of the need to pump up the performance of the complex query.

These really are meant primarily for diagnostic purposes. As a last
resort, you could set them off right before running a problem query,
and set them back on again afterward; but you will be much better off
if you can cure the underlying problem. The best chance of that is to
show us the plan you get with all turned on.

-Kevin

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Kevin Grittner 2009-06-16 15:48:30 Re: performance with query
Previous Message Alberto Dalmaso 2009-06-16 15:31:56 Re: performance with query