Re: Temp table or normal table for performance? - Mailing list pgsql-general

From Grzegorz Jaśkiewicz
Subject Re: Temp table or normal table for performance?
Date
Msg-id 2f4958ff0908210613w5c777cfcxca301719f539cd50@mail.gmail.com
Whole thread Raw
In response to Re: Temp table or normal table for performance?  (Jasen Betts <jasen@xnet.co.nz>)
List pgsql-general
On Thu, Aug 20, 2009 at 2:43 PM, Jasen Betts<jasen@xnet.co.nz> wrote:
> On 2009-08-19, Stephen Cook <sclists@gmail.com> wrote:
>
>> Let's say I have a function that needs to collect some data from various
>> tables and process and sort them to be returned to the user.
>
> plpgsql functions don't play well with temp tables IME.
> there are work-arounds and they are ugly. if you caus use a different
> language it could work.
it does on 8.3, prior versions have known flow.


It makes a lot of sense to use TT if you pass a lot of data back and
forth. It makes sense to open transaction, stick data into temp table,
and pass that around. Or even, in some cases, for duration of
connection - instead of storing data in client app.

pgsql-general by date:

Previous
From: Ivan Sergio Borgonovo
Date:
Subject: Re: Temp table or normal table for performance?
Next
From: Greg Stark
Date:
Subject: Re: join from array or cursor