Raf <[EMAIL PROTECTED]> writes:
> The final step was the decrement the reltriggers counter for the parent
> table's pg_class entry to 0. This appears to have resolved the problem.
You should probably have set it to 3 not 0; what you did has disabled
*all* the triggers on that table. Is that really what you want?
> I'm curious as to whether the problem may have resulted from slony
> corruptting internal pg_<tables> or postgres not correctly respecting the
> integrity of drop-trigger type transactions and their respective
> dependencies.
You'd be better off asking about that on the Slony mailing lists.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
