On Friday 18 March 2005 14:29, Stephan Szabo wrote: > Given the error message, this seems to be the whole plpgsql caches query > plans but we don't invalidate those plans when there are schema changes.
I already tried to execute the 'CREATE TEMP TABLE' statement using EXECUTE to avoid cache problems - same problem! ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match