Thu Mar 25 09:39:31 PDT 2010
- Previous message: [Slony1-general] How sensible is turning off synchronous_commit on a Slony slave while leaving it on on the master?
- Next message: [Slony1-general] Slony performace issues and an idea
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Vick, > Can you run arbitrary queries via your Qt wrapper? If so, then run a > "SET SESSION" disable of the synchronous commit, not per-transaction. > Then you get the benefit of it for that whole session without having > to enable it globally. Yes, I can. I wasn't aware it could be set on a session basis. I see that I can: SET synchronous_commit = false; from within my application. This seems far more sensible than forcing asynchronous commit on Slony and other remote clients of my slave dbs, of which there are several. Thanks, Peter Geoghegan
- Previous message: [Slony1-general] How sensible is turning off synchronous_commit on a Slony slave while leaving it on on the master?
- Next message: [Slony1-general] Slony performace issues and an idea
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list