From: Jim C. Nasby <jnasby@pervasive.com>
To: Markus Schiltknecht <markus@bluegap.ch>
Cc: alfranio correia junior <alfranio@lsd.di.uminho.pt>
Cc: Christopher Browne <cbbrowne@acm.org>
Cc: pgsql-hackers@postgresql.org
Subject: Re: standard interfaces for replication providers
Date: Wed, 9 Aug 2006 13:56:09 -0500
Message-ID: <20060809185609.GK40481@pervasive.com> (raw)
In-Reply-To: <44D98FCF.90408@bluegap.ch>
References: <44D30B31.2070403@lsd.di.uminho.pt>
<200608041733.24228.jop@lsd.di.uminho.pt>
<44D70EDA.9060602@bluegap.ch>
<200608071940.26750.jop@lsd.di.uminho.pt>
<44D89EA5.5090703@bluegap.ch>
<87irl3uqgx.fsf@wolfe.cbbrowne.com>
<44D8D334.5050808@bluegap.ch>
<44D8D9DE.50000@lsd.di.uminho.pt>
<44D98FCF.90408@bluegap.ch>
On Wed, Aug 09, 2006 at 07:33:35AM +0000, Markus Schiltknecht wrote:
> Hello Alfranio,
>
> alfranio correia junior wrote:
> >Of course not...
> >It is impossible to build a replication system entirely by only using
> >triggers...
>
> Hm, I don't think it's impossible, just unpractical. Anyway, if you say
> so yourself, I really doubt the use of GAPI. If you need to create your
> own hooks anyway beside GAPI, why use GAPI at all? Better have one kind
> of 'hooking' (i.e. with a dynamically loaded library).
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. Likewise, if there were hooks for WAL
records and a way to inject WAL info into a backend it probably wouldn't
be too hard to build WAL-based replication on top of that. Heck, PITR
could probably be refactored to use such hooks.
One of the great things about Oracle is that they expose a hell of a lot
of the technology they use to build features like replication; ie: take
a look at DBMS_*.
> >But definitely, there is a set of common requirements among a variety of
> >replication systems. Moreover, such requirements are also useful to
> >other systems as well.
>
> So far, they are only partly usable for replication. I never looked into
> materialized views or anything else that would benefit from such triggers.
>
> Regards
>
> Markus
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: jnasby@pervasive.com, markus@bluegap.ch, alfranio@lsd.di.uminho.pt, cbbrowne@acm.org
Subject: Re: standard interfaces for replication providers
In-Reply-To: <20060809185609.GK40481@pervasive.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox