Hello, I'm currently trying to set up the following architecture:
-- B subscribes to A -- B creates slony logshipper files -- Separate rsync process ships files from B to C -- C replays logshipper files -- D subscribes to C Problem is, even though D is subscribed to C, no data changes are made on D. I've discovered the cause to be from the logshipper files--at the top of each file is the command "set session_replication_role to replica," which effectively turns off the triggers, thereby preventing events from being propagated from C to D. My question is, how dangerous is it to remove the command "set session_replication_role to replica" from each logfile? Is this required? Right now, I'm removing them by doing cat $logfile | grep -v "set session_replication_role to replica" | psql <dbname...etc>. Works for my purposes, but I was curious to know if there are some really bad implications to this...there must be a reason why the command shows up at the top of each file. Any thoughts? --Richard _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
