Content-Type: text/plain;
  charset="iso-8859-1"
From: Richard Huxton <dev@archonet.com>
Organization: Archonet Ltd
To: "Vijay Kumar" <vijay@kinera.com>, <pgsql-sql@postgresql.org>
Subject: Re: Problem with temporary table -- Urgent
Date: Sat, 12 Jul 2003 09:45:35 +0100
User-Agent: KMail/1.4.3
References: <000801c346be$cf166db0$cf01a8c0@vijay>
In-Reply-To: <000801c346be$cf166db0$cf01a8c0@vijay>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200307120945.36058.dev@archonet.com>

On Thursday 10 Jul 2003 9:39 am, Vijay Kumar wrote:
> Hi,
> We are using postgresql 7.3.3, we are encountering the following problems
> when we used temporary tables.
>
> Here with i'm sending my Sample function.
>
> create or replace function TestTemp_refcur(refcursor) returns refcursor As
[snip]
>         lString  :=3D lString ||  '' create temporary table temp_Table( N=
ame
> Numeric);'';
[snip]
>  open refc for select * from temp_Table;
[snip]
> psql:test18.sql:25: ERROR:  Relation "temp_table" does not exist

Sorry about the delay.

The issue is that plpgsql is compiled, so the "open refc ... temp_Table"=20
refers to a specific entry in the system-tables. When the temp-table gets=
=20
recreated it gets a new OID and so your function can't find it.

Solution:
1. Don't use temp-tables
2. Use EXECUTE "..." which gets parsed when the function is run.

Note that this problem applies to any table that gets dropped and restored.=
 I=20
try to keep my function code in the same file as the table(s) they rely on,=
=20
that way I recreate both when I make changes.

--=20
  Richard Huxton