Folks,

I'd swear somebody committed a fix for the issue with temp tables inside
plpgsql functions, like, months ago. Yet I still get:

ERROR: relation with OID 16607 does not exist
CONTEXT: SQL statement "INSERT INTO tmp_runs ( run_id, batch, machine )
VALUES ( NEXTVAL('runs_run_id_seq'), $1 , $2 [ $3 ] )"
PL/pgSQL function "generate_test_series" line 67 at SQL statement
ERROR: relation with OID 16607 does not exist

This is CVS as of a week ago.

--
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Josh Berkus <josh (AT) agliodbs (DOT) com> writes:
Nope.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

On Thu, 2005-12-15 at 11:09 -0800, Jim Klo wrote:
Only the workarounds that have always existed: drop and recreate the
function, disconnect and then reconnect the client application, or
reference the temp table using EXECUTE only. The underlying problem
(invalidation of cached query plans) has not yet been fixed.

-Neil



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