Re: Proposal: Commit timestamp - Mailing list pgsql-hackers

From Richard Troy
Subject Re: Proposal: Commit timestamp
Date
Msg-id Pine.LNX.4.33.0702091223150.13334-100000@denzel.in
Whole thread Raw
In response to Re: Proposal: Commit timestamp  (Jan Wieck <JanWieck@Yahoo.com>)
List pgsql-hackers
On Fri, 9 Feb 2007, Jan Wieck wrote:
>
> No matter how many different models you have in parallel, one single
> transaction will be either a master, a slave or an isolated local thing.
> The proposed changes allow to tell the session which of these three
> roles it is playing and the triggers and rules can be configured to fire
> during master/local role, slave role, always or never. That
> functionality will work for master-slave as well as multi-master.
>
> Although my current plan isn't creating such a blended system, the
> proposed trigger and rule changes are designed to support exactly that
> in a 100% backward compatible way.
>
> Jan

Fantastic! ...At some point you'll be thinking of the management end -
turning it on or off, etc. That might be where these other points come
more into play.

Richard

-- 
Richard Troy, Chief Scientist
Science Tools Corporation
510-924-1363 or 202-747-1263
rtroy@ScienceTools.com, http://ScienceTools.com/



pgsql-hackers by date:

Previous
From: Richard Troy
Date:
Subject: Re: Proposal: Commit timestamp
Next
From: "Simon Riggs"
Date:
Subject: Re: Re-ordering of OR conditions