Thu Jul 3 00:55:39 PDT 2008
- Previous message: [Slony1-general] fail over failed
- Next message: [Slony1-general] how to prevent EXECUTE SCRIPT from locking all tables
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Don't remember. it's a while now. I could test it again but i have no time for that by now. sorry. May a big load on postgres (numerous instance of databases, other slony cluster) may cause side effects such this one? I already faced the famous "WARN remoteWorkerThread_1: transactions earlier than XID XXXXX are still in progress" on my loaded postgres. And of course no idea what is XXXXX ... Note since i'm testing my slonik scripts on my slony cluster on a brand new postgres, fail over and subscriptions are working properly. Whoever logged any other experience on side effects due to load on postgres is welcome.. 2008/7/2, Andrew Sullivan <ajs at crankycanuck.ca>: > > On Tue, Jul 01, 2008 at 11:50:29AM +0200, lio bod wrote: > > > > Subscription for set 1 is not active? My replication seems ok. At least > it > > replicates... > > So i don't understand the message > > What could be wrong on this fail over? > > What does sl_set say? > > A > _______________________________________________ > Slony1-general mailing list > Slony1-general at lists.slony.info > http://lists.slony.info/mailman/listinfo/slony1-general > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20080703/= cd23e7de/attachment.htm
- Previous message: [Slony1-general] fail over failed
- Next message: [Slony1-general] how to prevent EXECUTE SCRIPT from locking all tables
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list