From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Dennis <pg-user(at)calico-consulting(dot)com>, postgres SQL <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: lifetime of temp schema versus compiled image of plpgsql proc |
Date: | 2004-04-23 02:16:01 |
Message-ID: | 14587.1082686561@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Dennis wrote:
>> So I should be using EXECUTE for all access to the temp tables? ie inserts,
>> and selects (in this case). Should I use execute for the table creation?
> All access from plpgsql functions for temp tables should use EXECUTE,
I think that advice is not correct nor relevant to Dennis' problem. You
need EXECUTE if you are dropping and recreating temp tables within the
lifetime of a single connection, but he didn't do that. Even if he did
do it and hasn't told us so, that does not explain why the error message
complains about the temp *schema* and not a temp table. There's
something very strange here, because the temp schema name for a given
session is definitely fixed for the life of the session.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-04-23 02:34:16 | Re: Is there an easy way to normalize-space with given string functions |
Previous Message | Tom Lane | 2004-04-23 02:06:09 | Re: lifetime of temp schema versus compiled image of plpgsql proc |