Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've restored a database which came from a server on which Slony was running. The server on which the database has been restored does not have Slony installed.

When the database restored, there were a lot of errors reported, with Slony related objects not getting created due to Slony related logins being missing. This I thought was not a problem, as losing the Slony objects didn't seem to matter, and infact seemed desirable.

However, now I've got an anoying, if not critical problem. Whenever one clicks on a table in the newly restored DB in PGAdmin, a Slony related error popup ... pops up.

The first one reads: "An error has occured: ERROR: function _rmscl.getlocalnodeid(unknown) does not exist"

I notice that under the Replication node in PGAdmin, that there is a Slony replication cluster. Trying to drop this cluster results in more object missing type errors.

Does anyone have any ideas how we can remove the last vestiges of Slony from this database?

share|improve this question
up vote 6 down vote accepted

Assuming you don't have a slon daemon running anymore, just drop the schema that was installed by Slony:


(Adjust the name.)

share|improve this answer
Brilliant, worked perfectly. Thanks. – Scott Herbert Jan 11 '11 at 21:55

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.