From: =?utf-8?q?Jos=C3=A9_Orlando_Pereira?= <jop@lsd.di.uminho.pt>
Organization: http://gsd.di.uminho.pt/members/jop
To: pgsql-hackers@postgresql.org,
 Markus Schiltknecht <markus@bluegap.ch>
Subject: Re: standard interfaces for replication providers
Date: Thu, 10 Aug 2006 15:00:15 +0100
User-Agent: KMail/1.9.3
Cc: Hannu Krosing <hannu@skype.net>, "Jim C. Nasby" <jnasby@pervasive.com>,
	alfranio correia junior <alfranio@lsd.di.uminho.pt>,
	Christopher Browne <cbbrowne@acm.org>
References: <44D30B31.2070403@lsd.di.uminho.pt>
	<20060809185609.GK40481@pervasive.com>
	<1155153468.5899.12.camel@localhost.localdomain>
In-Reply-To: <1155153468.5899.12.camel@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200608101500.16468.jop@lsd.di.uminho.pt>

On Wednesday 09 August 2006 20:57, Hannu Krosing wrote:
> >
> > Why reinvent the wheel for everything if there was an interface that
> > offered some of the needed functionality? Maybe PostgreSQL-R is simply
> > too deep in the database for any of this to be useful, but I'm 99%
> > certain that Slony could make use of some of this stuff, such as a hook
> > on tuples being written out.
>
> Slonys problems ar *not* in getting access to tuples written out. Why
> fix something that aint broken ?

The current implementation of GAPI on PostgreSQL uses the same approach as 
Slony-I to extract the write-set. The difference is that it can push them out 
immediatly on commit, as required for eager update.

-- 
Jose Orlando Pereira