We've just started seeing these errors. Research I've done seems to
indicate that it's related to temp tables. Question is, we didn't start
seeing these errors until we started using slony to replicate our data.
The errors only showed up shortly after the initial replication of the
data was complete. That is, once the replication server 'caught up'
with the production server.
I posted to the slony list about this issue, but didn't get any bites.
--
Until later, Geoffrey
Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
- Benjamin Franklin
