Andrew Sullivan wrote:
On Tue, Feb 19, 2008 at 06:57:20PM -0500, Geoffrey wrote:
Apparently there were 100's of these errors generated, yet, when
researching the production data, it does not appear that there was any
corruption. Here is the text of one of the errors:
relation with OID 394006 does not exist
Aha! I'll bet lunch someone was doing DDL in their "shuffling data around".
That is an error message telling you that a previously-planned query is
looking for a now-dropped relation. One way to get this is indeed with temp
tables, but you can get it by dropping regular tables &c. I'd have a very
good look at how that procedure from last Friday worked.
If you do DDL under Slony without passing it through EXECUTE SCRIPT, you
_will_ get very strange results.
I only wish that was the problem. Our application does not remove any
tables.
--
Until later, Geoffrey
Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
- Benjamin Franklin
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general
