On Tue, 28 Oct 2008 19:46:42 +0200
Hannu Krosing <hannu(at)2ndQuadrant(dot)com> wrote:
> > The current topics are:
> > * New MCP architecture
> What's new ?
> I have some doubts about the current architecture based on my reading
> of replicator wiki, but would like to learn about the "new"
> architecture before spending too much time in studying the "old" one.
The two obvious problems with the existing MCP architecture is:
1. Single point of failure
The new architecture is set to remove both of those. The short version
is the MCP will be moved into the backend. Thus:
The process being, Master sends data to MCP|Slave, MCP|Slave writes it
to disk (optionally restores it) and then forwards it to 1,2,3 who then
receive the data, write it to disk and then restore it.
If master dies, you can promote to any of the slaves and the left over
slaves will connect to the promoted slave and begin receiving updates.
If the MCP|Slave dies a new Slave can begin the MCP|Slave process.
Alvaro or Alexey can speak more technically about implementation than I
> > * DDL Replication
> Is it there alread, or is it just a planned feature ?
> * How hard would it be to extract DDL replication part and use it as
> basis for DDL after trigger support for use in trigger based
> replication/auditing like Slony ann pgQ/Londiste ?
Hmm I am not sure. We are pretty deep into the core and only use
triggers for GRANT/REVOKE/CREATE ROLE .
Joshua D. Drake
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
United States PostgreSQL Association: http://www.postgresql.us/
In response to
pgsql-hackers by date
|Next:||From: Bruce McAlister||Date: 2008-10-28 23:01:33|
|Subject: UUID-OSSP Contrib Module Compilation Issue|
|Previous:||From: Martin Pihlak||Date: 2008-10-28 22:15:38|
|Subject: Re: SQL/MED compatible connection manager|