Maxim Boguk <mboguk@xxxxxxxxxxxxx> writes: > Server was slave in slony replication. > Now problem: > table was unsubscribed from replication (without any errors) > and then dropped from master without any errors > But when i try drop table from slave i got very strange error: > hh=# drop TABLE metro_station_old; > ERROR: "area_pk" is an index You'd be best off to ask about this on the Slony mailing lists. Slony plays some strange games with the system catalogs, and I think that cases like this are fairly common if you don't perform schema changes on slon-ified tables in just exactly the right way. Hopefully somebody over there will recognize this particular symptom and help you out. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
