Hi Steve,
	A question on one item:

        - Fix some failover issues when doing a multi-node failover
          with a cascaded node.

	In cascaded node failover, is it necessary to sync with every receiver node for a failed over set? Or is it sufficient to sync only with nodes directly subscribing to the failed over node? Hoping for the latter!
	Thanks,
	
	Tom    (


On 7/30/17, 10:15 PM, "Steve Singer" <steve at ssinger.info> wrote:

    
    I am thinking of releasing slony 2.2.6 later this week or early next week.
    Changes are checked into git on the REL_2_2_STABLE branch.
    
    Our version detection code doesn't work with the PG10+ version numbering. I 
    wasn't planning on backporting these changes to 2.1 or earlier but someone 
    could if they really wanted to.
    
    
    The following are the changes I am planning on including in 2.2.6
    
       - slonik_build_env can now accept multiple -schema options on the command 
    line
        - Support for PG10. This involved changes to PG version detection
        - Disallow createEvent and data changes in the same transaction.
          This also fixes some issues when the logApply trigger invokes the
          data change trigger by inserting into a table with a trigger that
          in turns inserts into another replicated table.
        - Fix some failover issues when doing a multi-node failover
          with a cascaded node.
        - Bug 341 - suppress log trigger/deny when running in 'local' mode
    
    
    
    If I don't hear any objections, or requests for more time to test I work 
    through the release process when I have a chance, likely Monday.
    
    Steve
    
    _______________________________________________
    Slony1-general mailing list
    Slony1-general at lists.slony.info
    http://lists.slony.info/mailman/listinfo/slony1-general