pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Dennis <pg-user@calico-consulting.com>
Cc: postgres SQL <pgsql-sql@postgresql.org>
Subject: Re: lifetime of temp schema versus compiled image of plpgsql proc
Date: Thu, 22 Apr 2004 22:16:01 -0400
Message-ID: <14587.1082686561@sss.pgh.pa.us> (raw)
In-Reply-To: <200404222354.i3MNsgF26021@candle.pha.pa.us>
References: <200404222354.i3MNsgF26021@candle.pha.pa.us>

Bruce Momjian <pgman@candle.pha.pa.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



view thread (7+ messages)  latest in thread

Message-ID: <14587.1082686561@sss.pgh.pa.us>
Permalink:  ../14587.1082686561@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/14587.1082686561@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us, pg-user@calico-consulting.com
  Subject: Re: lifetime of temp schema versus compiled image of plpgsql proc
  In-Reply-To: <14587.1082686561@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox