Chris Bowlby wrote: > Using a temporary table of the same name in repeated calls to a stored > procedure are causing OID failure issues, it can be re-created using the > following useless example:
This is an unfortunate side-effect of caching access plans in PL/PgSQL functions, see FAQ: http://www.postgresql.org/docs/faqs.FAQ.html#item4.19 The upcoming 8.3 release will include plan invalidation, which will fix this issue. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
