Re: Important speed difference between a query and a

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: Frederic Jolliton <fred-pg(at)jolliton(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Important speed difference between a query and a
Date: 2003-04-24 17:28:08
Message-ID: 20030424101802.M2131-100000@megazone23.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, 24 Apr 2003, Frederic Jolliton wrote:

> > On Thu, 24 Apr 2003, Frederic Jolliton wrote:
> > Perhaps plpgsql with EXECUTE would work better for that, although
> > it's likely to have some general overhead.
>
> The server is rather fast, and the query return 10 to 50 rows in most
> case. So, this is probably a solution, even if it's not very
> clean. (Well, I have to find an example to RETURN the result of
> EXECUTE..)

Check out
http://techdocs.postgresql.org/guides/SetReturningFunctions

specifically the GetRows() function for an example of using for in execute
with set returning functions.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Frederic Jolliton 2003-04-24 17:40:17 Re: Important speed difference between a query and a
Previous Message Frederic Jolliton 2003-04-24 16:41:49 Re: Important speed difference between a query and a