Hi guys,

I started a replication between master and a slave using slony 1.2.21. The
replication went succesfully and then i killed the slon daemons on both
machines. After that i wanted to remove the _replication schemas from the
database to remove all the traces of the replication schema and tables from
the database. So i went ahead and did "Drop schema _rep_cluster CASCADE" on
the slave first. It removed _rep_cluster schema from the slave completely
and then i went to do the same on the master node but there i was stuck on -
ERROR: "table_pkey" is an index. Now 'table' is the name of one of my tables
on the database and table_pkey is the associated primary key with it i
guess.

Has anybody seen this error before? Did the slony lock down itself because i
did not remove the schema correctly?

Currently there is a fully functioning replication going on from slave to
master with a different rep_diff_cluster for tables(a , b) and then from
master to slave for different 2 more tables (c, d) which is the main
replication we wanted after the initial small replication from master to
slave( a, b) (whose schema i wanted to remove from the databases completely)

Regards
Dilraj Singh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20110926/a73d80dc/attachment.htm