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

           Summary: In the event of OID mismatch, slon confirms
                    replication events without actually actioning them
           Product: Slony-I
           Version: 2.0
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: low
         Component: slon
        AssignedTo: slony1-bugs at lists.slony.info
        ReportedBy: womagrid at gmail.com
                CC: slony1-bugs at lists.slony.info
   Estimated Hours: 0.0


1) Create any Slony cluster e.g. 1 x master, 1 x slave, 1 x set

2) On the slave, stop slon

3) On the slave, perform an operation that invalidates an OID stored in
sl_table or sl_sequence e.g. DROP TABLE <table> and CREATE TABLE <table>

4) On the slave, start slon

The Slony log will show that the slave's slon is receiving replication and
events and also confirming them.  The problem is that none of the changes are
actually being applied on the slave due to the mismatched OID.

5) Fix the OID in sl_path or sl_sequence after obtaining the correct OID from
pg_class (presumably this could also be done via slonik_repair_config)

6) Restart slon on the slave

Now, new events are confirmed AND actioned but the events that were previously
confirmed are lost forever.

Effectively, replication events are skipped over and cannot be replayed.  The
only option is to resync the slave.

Suggestion: slon should not confirm replication events involving a relation
with mismatched OID but instead log an error.

This would create the opportunity for a manual repair of the mismatched OID,
after which all lagging events would be actioned and slave sync could be
restored with minimal effort.

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