Postgres Pro
Downloads
Home   >   mailing lists

Re: storing intermediate results in recursive plpgsql functions - Mailing list pgsql-general

From Tom Lane
Subject Re: storing intermediate results in recursive plpgsql functions
Date
Msg-id 2514.1015021461@sss.pgh.pa.us
Whole thread Raw
In response to storing intermediate results in recursive plpgsql functions  (Fran Fabrizio <ffabrizio@mmrd.com>)
List pgsql-general
Tree view 
Fran Fabrizio <ffabrizio@mmrd.com> writes:
> I feel like I'm missing something obvious.

Well, you could use a temp table if you access it via EXECUTEd commands.
Or you could use a non-temp table and just not unlock; let the unlock
happen at normal end of transaction.  The latter is probably easier.

            regards, tom lane

pgsql-general by date:

Previous
From: Francisco Reyes
Date:
Subject: Re: Is vacuum full lock like old's vacuum's lock?
Next
From: "Greg Sabino Mullane"
Date:
Subject: PostgreSQL favicon.ico