Re: Performance problem on RH7.1

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: csegyud(at)vnet(dot)hu
Cc: "'Alvaro Herrera'" <alvherre(at)dcc(dot)uchile(dot)cl>, "'Pgsql-General(at)Postgresql(dot)Org (E-mail)'" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Performance problem on RH7.1
Date: 2004-06-28 18:10:22
Message-ID: 29248.1088446222@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

=?iso-8859-2?Q?Egy=FCd_Csaba?= <csegyud(at)vnet(dot)hu> writes:
>> I'd also suggest dropping the EXECUTE approach, as this is costing you
>> a re-plan on every call without buying much of anything.

> Do you mean I should use PERFORM instead? Or what else?
> Do you mean the "for R in execute" statements? How can I run a dynamic query
> in other way?

No, I mean the most straightforward way:

for R in select ... where stockid = $1 and ...

This lets plpgsql cache the plan for the SELECT.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scrappy 2004-06-28 18:17:39 Re: Text message
Previous Message Tom Lane 2004-06-28 18:04:59 Re: Inconsistant DOW...