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

           Summary: Slony-I: old key column tbl_stock_2012.comments IS
                    NULL on UPDATE
           Product: Slony-I
           Version: 1.2
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: blocker
          Priority: low
         Component: slon
        AssignedTo: slony1-bugs at lists.slony.info
        ReportedBy: kndee at hotmail.com
                CC: slony1-bugs at lists.slony.info
   Estimated Hours: 0.0


I have been using Slony (Version - 1.2.20) with Postgres (Version 8.2.13)
successfully for over two years.

I had few new columns added to the tables in the replication. As my usual
practice, I first added the columns in slave DB and thereafter in the master
DB. 

After adding, I started getting the following error intermittently and failing
any updates to this table - tbl_stock_2012 :

          Slony-I: old key column tbl_stock_2012.comments IS NULL on UPDATE.

I could not think of a reason as the DDL is similar in both master and slave
and other configurations are also identical. I have not done any other changes
to Slony or the replication set recently or updated Slony software.

I think this issue is similar to that of BUG 67 or BUG 73, if so, what I could
do to resolve this issue in Slony version 1.2 ?

Let me know if I need to provide  more information to describe the issue.

-- 
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.