On Wed, Feb 10, 2010 at 4:47 AM, Koen Martens <gmc at sonologic.nl> wrote:
> To answer my own question: it seems there is some lingering cache somehwere,
> as a restart of PostgreSQL before re-installing slony did the trick.
>

It would have been sufficient to kill all open connections to the
server (ie, restart the apps) because they seem to have connected to
your DB before you did the delete of slony from your DB.  They had
cached plans with the slony triggers.