Thu Dec 11 12:32:48 PST 2014
- Previous message: [Slony1-general] Slonik lock set, verifying
- Next message: [Slony1-general] PGRES_FATAL_ERROR ERROR: could not access file "$libdir/slony1_funcs.2.2.3": No such file or directory
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Well, when slony gets around to the cases where it needs to alter tables, it'll be a problem if it's fighting for exclusive locks against the requests for lesser locks by the read-oriented connections. But the crucial thing about the LOCK SET is that it forcibly prevents data from going into the replicated tables so that the queue of updates in sl_log_{1|2} are able to flush with the guarantee that no more data goes in. So I'd say the reads aren't 100% unaffected; they're 95% unaffected. (And the 5% represents "I WANT EXCLUSIVE LOCKS, NOW!!! Gotta finish this upgrade!") Hopefully that helps? Knowing what the 5% is represents the battle! :-) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20141211/ecf843a2/attachment.htm
- Previous message: [Slony1-general] Slonik lock set, verifying
- Next message: [Slony1-general] PGRES_FATAL_ERROR ERROR: could not access file "$libdir/slony1_funcs.2.2.3": No such file or directory
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list