Thu Sep 6 08:41:12 PDT 2007
- Previous message: [Slony1-general] SYNCs with no subscribers + log switching problems?
- Next message: [Slony1-general] failover doesn't remove triggers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Vivek Khera <vivek at khera.org> writes: > On Sep 5, 2007, at 10:39 PM, Jan Wieck wrote: > >> On 9/4/2007 9:53 PM, Dan Falconer wrote: >>> I was then struck by yet another surprise: Slony seems to like >>> keeping all it's log data, even when it's the only running node. >>> I've noticed there have >> >> The case of having a replication set but no subscribers at all is a >> little pathologic and not optimized for especially. > > I ran into this in a 2-node setup when the replica failed and had to > have hardware replaced. The only way out was to uninstall slony from > the origin server, and then re-configure everything from scratch. > > I recall either Chris or Jan saying roughly the same thing about it > not being a tested normal operation case at that time, too :-) There was code changed for this a while back, so I think this is likely a version-dependent issue. This went into src/base/slony1_funcs.sql, in version 1.82, which was committed 2006-03-28, in HEAD. This should therefore be in the 1.2 branch. It won't be in the 1.1 branch... -- let name="cbbrowne" and tld="linuxfinances.info" in name ^ "@" ^ tld;; http://linuxdatabases.info/info/sap.html Signs of a Klingon Programmer - 12. "You question the worthiness of my code? I should kill you where you stand!"
- Previous message: [Slony1-general] SYNCs with no subscribers + log switching problems?
- Next message: [Slony1-general] failover doesn't remove triggers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list