From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
---|---|
To: | ivan <iv(at)psycho(dot)pl> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: cache in plpgsql |
Date: | 2003-12-31 12:50:16 |
Message-ID: | 3FF2C608.3090906@Yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Gaetano Mendola | 2003-12-31 12:54:00 | Re: Preventing stack-overflow crashes (improving on max_expr_depth) |
Previous Message | Greg Sabino Mullane | 2003-12-31 12:01:55 | Re: PostgreSQL speakers needed for OSCON 2004 |