Message-ID: <3FF2C608.3090906@Yahoo.com>
Date: Wed, 31 Dec 2003 07:50:16 -0500
From: Jan Wieck <JanWieck@Yahoo.com>
Organization: Home
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624
MIME-Version: 1.0
To: ivan <iv@psycho.pl>
Cc: pgsql-hackers@postgresql.org
Subject: Re: cache in plpgsql
References: <Pine.LNX.4.56.0312302329590.5131@rex.anfa.pl>
In-Reply-To: <Pine.LNX.4.56.0312302329590.5131@rex.anfa.pl>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

ivan wrote:

>as new know plpgsql has special cache which remember too long (event
>non-existing tables (i mean old oid)) so i suggest to create same function
>only in plpgsql which would clear this cache, or sth like this ?
>
>for ie, where i drop table i would do plpgsql_clear_cache ();
>and when i will create one more time table with this same name plpgsql
>will not remeber wrong oid
>
>possible ?
>  
>

You obviously did not bother to search the archives on this.

This will not solve the problem since the "cache" you're talking about 
is per backend local memory. So if one backend modifies the schema, how 
does it cause all other to forgt? Since the same problem exists in 
general for everything that uses SPI, the solution lies in there.


Jan

-- 

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #