http://www.slony.info/bugzilla/show_bug.cgi?id=266

--- Comment #2 from Jan Wieck <janwieck at yahoo.com> 2012-05-16 06:47:31 PDT ---
This isn't anything we could fix in 1.2 anyway.

I presume that you dropped some columns that physically appeared before the key
column(s) used by Slony to identify rows. Even if you added them back later,
the physical order of columns has changed and the log trigger's idea of which
columns are key columns is out of sync with the current table structure.

The really bad news is that this may already have corrupted data on your
replica. Let me assume that tbl_stock_2012 had only one key column and that now
comments is wrongly used as that key column. Any update or delete where
comments is not NULL will succeed properly on the origin, but will then
update/delete all rows on the replica that have that same value in comments.

You will need to verify that the tables are still in sync or consider
rebuilding the replication setup from scratch.

-- 
Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.