Kris,
thanks for the reply. I dont actually use temp tables in the function (not that I know of) but I did truncated and reloaded a few tables incl. recreating indices the previous day, however the line no. indicated in the serverlog does not point to these sql calls.


I am now re-starting tomcat every night which is not a bad thing anyway but still am wondering what the real reason could be.

Alex

Kris Jurka wrote:

On Tue, 20 Jan 2004, Alex wrote:



Hi,
I am getting the following error when running an update from a JAVA
program using a Tomcat Connection Pool.

SQLException: Error Relation 215106760 does not exist

In the server log I see additional info Error occured while executing
PL/pgSQL function funcName
line 105 at select into variables



This error is likely the result of using a temp table without EXECUTE or having one of your tables dropped (recreating it won't help). plpgsql caches query plans, but doesn't track the plans dependencies, so if any of the underlying objects change you can get this error.



2. Could this be a problem with the connection pool of tomcat or the
postgres JDBC driver ?



The plans are cached once per backend, the connection pool keeps that same backend open forever which means you can never safely change your schema without restarting the pool.



3. how do i find out the name of the actual object referred by 215106760
in the error message?




SELECT relname FROM pg_class WHERE oid = 215106760;


Kris Jurka


---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend







---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Reply via email to