From: | Hannu Krosing <hannu(at)2ndquadrant(dot)com> |
---|---|
To: | Marko Kreen <markokr(at)gmail(dot)com> |
Cc: | Jan Wieck <JanWieck(at)yahoo(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-cluster-hackers(at)postgresql(dot)org |
Subject: | Re: Clustering features for upcoming developer meeting -- please claim yours! |
Date: | 2010-05-10 22:48:13 |
Message-ID: | 1273531693.15431.66.camel@hvost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-cluster-hackers |
On Tue, 2010-05-11 at 01:08 +0300, Marko Kreen wrote:
> On 5/11/10, Jan Wieck <JanWieck(at)yahoo(dot)com> wrote:
> > This means that a generalized data queue needs to have hooks, so that DDL
> > triggers can inject their payload into it.
>
> If you mean "hooks" as pgq.insert_event() function, then yes..
> I hope you are designing a generally usable queue with the GDQ.
The only way to have a generally usable queue different from pgQ is
having something that copies all events off the server (to either final
subscriber or some forwarding/processing station) and leaves the
commit/abort resolution to "the other server".
event id should still provide an usable order for applying these events.
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2010-05-11 02:46:24 | Re: Clustering features for upcoming developer meeting -- please claim yours! |
Previous Message | Hannu Krosing | 2010-05-10 22:40:21 | Re: Clustering features for upcoming developer meeting -- please claim yours! |