Re: standard interfaces for replication providers

>  
> 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.
>   
Yeah !!!
:-)
The idea is to provide means to inject things at different levels
(statement,
parsed statements, plans, tuples, logs -wal).
So the GAPI provides a generic and standard interface
that enables any application to retrieve information at different
levels and inject information at different levels.

> 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_*.
>   
If I am not wrong such procedures are only for administrative purpose.
For instance,
we cannot insert things in a queue to be replicated.