X-Original-To: pgsql-hackers-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 9DB239FB206 for ; Mon, 7 Aug 2006 15:44:24 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 84034-01 for ; Mon, 7 Aug 2006 18:44:15 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from dcs.lsd.di.uminho.pt (linux.di.uminho.pt [193.136.19.96]) by postgresql.org (Postfix) with ESMTP id 0D52E9FA4E0 for ; Mon, 7 Aug 2006 15:44:14 -0300 (ADT) Received: (qmail 23741 invoked by uid 89); 7 Aug 2006 18:44:40 -0000 Received: from unknown (HELO localhost.localdomain) (192.168.82.189) by dcs.lsd.di.uminho.pt with SMTP; 7 Aug 2006 18:44:40 -0000 From: Jose Orlando Pereira Organization: http://gsd.di.uminho.pt/members/jop To: pgsql-hackers@postgresql.org Subject: Re: standard interfaces for replication providers Date: Mon, 7 Aug 2006 19:40:26 +0100 User-Agent: KMail/1.9.3 Cc: Markus Schiltknecht , Josh Berkus , alfranio@lsd.di.uminho.pt References: <44D30B31.2070403@lsd.di.uminho.pt> <200608041733.24228.jop@lsd.di.uminho.pt> <44D70EDA.9060602@bluegap.ch> In-Reply-To: <44D70EDA.9060602@bluegap.ch> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <200608071940.26750.jop@lsd.di.uminho.pt> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.72 tagged_above=0 required=5 tests=SARE_SPEC_REPLICA X-Spam-Level: X-Archive-Number: 200608/437 X-Sequence-Number: 87930 On Monday 07 August 2006 10:58, Markus Schiltknecht wrote: > > Where do I find the included technical report? Sorry, stuff was put twice in the zip file making it somewhat confusing. It is in postgresql-g-0.1/javasrc/GordaInterfaces/docs/gapi.pdf or directly on the web site at http://gorda.di.uminho.pt/download/reports/gapi.pdf. > From studying the patch, I understand that these hooks are quite close > to what's needed for a Postgres-R or Slony-II like sync, multi-master > replication system (i.e. hooks for writeset extraction, the addition of > a 'serialization error' for remote transactions). Good. Supporting Postgres-R-style protocols was one major goal of our work. > In fact, Postgres-R (8) would already need different hooks. > Concerning my work on Postgres-R I can tell: I'm not going to use these > triggers (hooks) because they are limiting. Can you point out why is it so, given that it is admittedly quite close? We'd rather discuss specific issues instead of the general topic of whether to build APIs around them. We certainly are not married to the proposed interfaces, although the functionality they capture does reflect our experience with several algorithms. -- Jose Orlando Pereira