Re: Standalone synchronous master
От | Jim Nasby |
---|---|
Тема | Re: Standalone synchronous master |
Дата | |
Msg-id | 52D4572D.2040802@nasby.net обсуждение исходный текст |
Ответ на | Re: Standalone synchronous master ("Joshua D. Drake" <jd@commandprompt.com>) |
Ответы |
Re: Standalone synchronous master
Re: Standalone synchronous master |
Список | pgsql-hackers |
On 1/13/14, 12:21 PM, Joshua D. Drake wrote: > > On 01/13/2014 10:12 AM, Hannu Krosing wrote: >>>> In other words, if we're going to have auto-degrade, the most >>>> intelligent place for it is in >>>> RepMgr/HandyRep/OmniPITR/pgPoolII/whatever. It's also the *easiest* >>>> place. Anything we do *inside* Postgres is going to have a really, >>>> really hard time determining when to degrade. >>> +1 >>> >>> This is also how 2PC works, btw - the database provides the building >>> blocks, i.e. PREPARE and COMMIT, and leaves it to a transaction manager >>> to deal with issues that require a whole-cluster perspective. >>> >> >> ++1 > > +1 Josh, what do you think of the upthread idea of being able to recover in-progress transactions that are waiting when we turnoff sync rep? I'm thinking that would be a very good feature to have... and it's not something you can easily do externally. -- Jim C. Nasby, Data Architect jim@nasby.net 512.569.9461 (cell) http://jim.nasby.net
В списке pgsql-hackers по дате отправления: