Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node
| От | Simon Riggs |
|---|---|
| Тема | Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node |
| Дата | |
| Msg-id | CA+U5nM+dm_K6bCXsM5B1K4mhuHM30j8N=07SVaP4vr2rczVYBA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
| Список | pgsql-hackers |
On 21 June 2012 03:13, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote: > On 20.06.2012 21:51, Simon Riggs wrote: >> >> On 21 June 2012 02:32, Heikki Linnakangas >> <heikki.linnakangas@enterprisedb.com> wrote: >>> >>> I'm not saying that we need to implement all possible conflict resolution >>> >>> algorithms right now - on the contrary I think conflict resolution >>> belongs >>> outside core >> >> >> It's a pretty standard requirement to have user defined conflict >> handling, if that's what you mean. >> >> I'm OK with conflict handling being outside of core as a module, if >> that's what people think. We just need a commit hook. That is more >> likely to allow a workable solution with 9.3 as well, ISTM. It's >> likely to be contentious... > > > Hmm, what do you need to happen at commit time? > > We already have RegisterXactCallback(), if that's enough... Let me refer back to my notes and discuss this later, I'm just going from vague memory here, which isn't helpful. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: