From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Joseph Shraibman <jks(at)selectacast(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: performance tuning |
Date: | 2002-12-04 12:15:00 |
Message-ID: | 20021204121500.GE9782@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Dec 03, 2002 at 09:48:46PM -0500, Joseph Shraibman wrote:
> Joseph Shraibman wrote:
> >Since postgres
> >seems to think that the nested loop takes so long do I have to lower
> >cpu_operator_cost to get postgres to use the nested loop?
>
> To answer my own question that doesn't work. I've kept playing around with
> different paramaters with different variables but I can't find anything
> except disabling seqscans.
>
> This is really annoying, because *all* of my queries suddenly slowed down
> at the same time. What can I do? Is there something I can change in the
> source to have nested loops seem cheaper? I haven't found anything.
What does explain analyze tell you?
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Support bacteria! They're the only culture some people have.
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Elphick | 2002-12-04 13:00:05 | Re: problem startting postgresql |
Previous Message | Jean-Christian Imbeault | 2002-12-04 11:56:10 | Re: pg and number of parameters by insert |