Hi,

Someone drop a FK constraint without using slonik (in slony1 1.2.20)
and inserted some rows in that table... some of those rows violate the
dropped constraint and obviously the replica can't insert the data
because in the replica the constraint still exist...

if i try to drop the constraint in the replica it says something about
a non related index (i guess this is because slony messed up
pg_trigger catalog for disabling triggers)...

i can't add the constraint in primary in order to properly drop it,
because there are rows violating the constraint... so i try to drop
the table from the replication set but because of the replica having
pending events that command is waiting in the queu...

so there is a way to solve this or i have to drop the replica and rebuild?

-- 
Jaime Casanova         www.2ndQuadrant.com
Soporte y capacitación de PostgreSQL