Fri Dec 9 13:56:48 PST 2011
- Previous message: [Slony1-general] Strange bug with slony 2.0.7 and postgresql 9.1.1
- Next message: [Slony1-general] Strange bug with slony 2.0.7 and postgresql 9.1.1
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Steve, Unfortunatelly I have no chance to test that patch now. Slony was used as a temporary solution to migrate db cluster between 9.0 and 9.1. And after that process were done, cluster returned to use hot-standby again. Sorry. Kind Regards, Maksym On Sat, Dec 10, 2011 at 3:58 AM, Steve Singer <ssinger at ca.afilias.info>wrote: > On 11-11-23 04:09 PM, Steve Singer wrote: > > Maxim, > > Did you ever check to see if this patch actually fixes your problem with > running Slony against 9.1.x? > > Did you encounter any other issues with it? > > > > > > On 11-11-23 09:27 AM, Simon Riggs wrote: >> >>> On Wed, Nov 23, 2011 at 1:51 PM, Steve Singer<ssinger at ca.afilias.info**> >>> wrote: >>> >>>> On 11-11-23 04:28 AM, Simon Riggs wrote: >>>> >>>>> >>>>> On Tue, Nov 22, 2011 at 10:26 PM, Steve Singer<ssinger at ca.afilias.info >>>>> **> >>>>> wrote: >>>>> >>>>>> >>>>>> On 11-11-20 05:47 AM, Cédric Villemain wrote: >>>>>> >>>>>>> >>>>>>> >>>> >>>>> ISTM that setting the remote worker to REPEATABLE READ would work well >>>>> for this case. Patch attached. >>>>> >>>>> >>>> Simon, Did you forget to attach the patch? I don't see it. >>>> >>> >>> Looks that way. >>> >>> >> Thanks for the patch. >> >> So why would a SERIALIZABLE READ ONLY DEFERRED transaction produce fewer >> conflicts than a READ COMMITTED transaction? Currently the >> remote_listener gets the default isolation level (READ COMMITTED). >> >> The attached patch combines your two patches plus performs the same >> change to other places in remote_worker (there are places in >> remote_worker.c where that initial transaction is rolledback and >> restarted, this version also makes sure that those transactions are >> started as READ COMMITTED). It also makes the connections that the >> remote helpers do to the remote database for querying sl_log_x READ ONLY >> DEFERRED. >> >> When I run this patch through the test suite on 9.1 I don't see any >> serialization pivot failures (at least not yet). >> >> > -- Maxim Boguk Senior Postgresql DBA. Phone RU: +7 910 405 4718 Phone AU: +61 45 218 5678 Skype: maxim.boguk Jabber: maxim.boguk at gmail.com LinkedIn profile: http://nz.linkedin.com/in/maximboguk If they can send one man to the moon... why can't they send them all? МойКруг: http://mboguk.moikrug.ru/ Сила солому ломит, но не все в нашей жизни - солома, да и сила далеко не все. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20111210/963d5679/attachment.htm
- Previous message: [Slony1-general] Strange bug with slony 2.0.7 and postgresql 9.1.1
- Next message: [Slony1-general] Strange bug with slony 2.0.7 and postgresql 9.1.1
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list