Re: [HACKERS] PostgreSQL + Replicator developer meeting 10/28

2008-11-03 Thread Alvaro Herrera
Hannu Krosing wrote: On Tue, 2008-10-28 at 22:37 -0300, Alvaro Herrera wrote: If you mean that we're duplicating the effort that's already going elsewhere, my opinion is yes, we are. duplicating the effort is not always a bad thing. I was mostly suggesting to watch discussions and dig

Re: [HACKERS] PostgreSQL + Replicator developer meeting 10/28

2008-10-29 Thread Hannu Krosing
On Tue, 2008-10-28 at 22:37 -0300, Alvaro Herrera wrote: Hannu Krosing wrote: On Tue, 2008-10-28 at 15:18 -0700, Joshua Drake wrote: The two obvious problems with the existing MCP architecture is: 1. Single point of failure For async replication there is always SPoF, at least

Re: [HACKERS] PostgreSQL + Replicator developer meeting 10/28

2008-10-29 Thread Hannu Krosing
On Tue, 2008-10-28 at 22:16 -0700, Joshua D. Drake wrote: Alvaro Herrera wrote: Hannu Krosing wrote: On Tue, 2008-10-28 at 15:18 -0700, Joshua Drake wrote: Will there be an helper application for setting up and configuring changes in replication. or will it all be done using added SQL

Re: [HACKERS] PostgreSQL + Replicator developer meeting 10/28

2008-10-29 Thread Andrew Sullivan
On Wed, Oct 29, 2008 at 12:02:20PM +0200, Hannu Krosing wrote: A good goal. But why would anybody _need_ 50 slaves ? They might have a contractual responsibility for extremely wide geographic distribution. Or they might be building an application that needs extremely wide network-topological

Re: [HACKERS] PostgreSQL + Replicator developer meeting 10/28

2008-10-29 Thread Joshua D. Drake
On Wed, 2008-10-29 at 12:02 +0200, Hannu Krosing wrote: On Tue, 2008-10-28 at 22:16 -0700, Joshua D. Drake wrote: Alvaro Herrera wrote: Case in point. To replicate a table currently you do this: ALTER TABLE foo ENABLE REPLICATION; ALTER TABLE foo ENABLE REPLICATION ON SLAVE 0; How

Re: [HACKERS] PostgreSQL + Replicator developer meeting 10/28

2008-10-29 Thread Joshua D. Drake
On Wed, 2008-10-29 at 09:54 +0200, Hannu Krosing wrote: On Tue, 2008-10-28 at 22:37 -0300, Alvaro Herrera wrote: Hannu Krosing wrote: On Tue, 2008-10-28 at 15:18 -0700, Joshua Drake wrote: it was in subsection mcp_server mysteriously dies

Re: [HACKERS] PostgreSQL + Replicator developer meeting 10/28

2008-10-29 Thread Hannu Krosing
On Wed, 2008-10-29 at 09:01 -0700, Joshua D. Drake wrote: On Wed, 2008-10-29 at 12:02 +0200, Hannu Krosing wrote: On Tue, 2008-10-28 at 22:16 -0700, Joshua D. Drake wrote: Alvaro Herrera wrote: Case in point. To replicate a table currently you do this: ALTER TABLE foo ENABLE

Re: [HACKERS] PostgreSQL + Replicator developer meeting 10/28

2008-10-29 Thread Joshua D. Drake
On Wed, 2008-10-29 at 19:15 +0200, Hannu Krosing wrote: SLAVE 0 is defined by a GUC on the slave, replication_slave_no I think. ( I would have to check the docs) And the only other GUC slave needs for replication is MCP/Slave connect info ?

Re: [HACKERS] PostgreSQL + Replicator developer meeting 10/28

2008-10-28 Thread Hannu Krosing
On Mon, 2008-10-27 at 13:42 -0700, Joshua Drake wrote: With the recent open sourcing of Replicator, the team has been trying to come up with ways to ensure an open development process. In that light we have decided to have our first release 1.9 meeting on Freenode. All people interested in

Re: [HACKERS] PostgreSQL + Replicator developer meeting 10/28

2008-10-28 Thread Joshua Drake
On Tue, 28 Oct 2008 19:46:42 +0200 Hannu Krosing [EMAIL PROTECTED] wrote: On Mon, 2008-10-27 at 13:42 -0700, Joshua Drake wrote: With the recent open sourcing of Replicator, the team has been trying to come up with ways to ensure an open development process. In that light we have decided

Re: [HACKERS] PostgreSQL + Replicator developer meeting 10/28

2008-10-28 Thread Devrim GÜNDÜZ
On Tue, 2008-10-28 at 19:46 +0200, Hannu Krosing wrote: * Is there a mailing list for replicator ? https://lists.commandprompt.com/mailman/listinfo/replicator-general Regards, -- Devrim GÜNDÜZ, RHCE devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr

Re: [HACKERS] PostgreSQL + Replicator developer meeting 10/28

2008-10-28 Thread Hannu Krosing
On Tue, 2008-10-28 at 11:01 -0700, Joshua Drake wrote: On Tue, 28 Oct 2008 19:46:42 +0200 Hannu Krosing [EMAIL PROTECTED] wrote: On Mon, 2008-10-27 at 13:42 -0700, Joshua Drake wrote: With the recent open sourcing of Replicator, the team has been trying to come up with ways to ensure

Re: [HACKERS] PostgreSQL + Replicator developer meeting 10/28

2008-10-28 Thread Joshua Drake
On Tue, 28 Oct 2008 19:46:42 +0200 Hannu Krosing [EMAIL PROTECTED] 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

Re: [HACKERS] PostgreSQL + Replicator developer meeting 10/28

2008-10-28 Thread Hannu Krosing
On Tue, 2008-10-28 at 15:18 -0700, Joshua Drake wrote: On Tue, 28 Oct 2008 19:46:42 +0200 Hannu Krosing [EMAIL PROTECTED] wrote: The current topics are: * New MCP architecture What's new ? I have some doubts about the current architecture based on my reading of

Re: [HACKERS] PostgreSQL + Replicator developer meeting 10/28

2008-10-28 Thread Alvaro Herrera
Hannu Krosing wrote: On Tue, 2008-10-28 at 15:18 -0700, Joshua Drake wrote: The two obvious problems with the existing MCP architecture is: 1. Single point of failure For async replication there is always SPoF, at least the master until first slave has aquired log is a SPoF, or do

Re: [HACKERS] PostgreSQL + Replicator developer meeting 10/28

2008-10-28 Thread Joshua D. Drake
Alvaro Herrera wrote: Hannu Krosing wrote: On Tue, 2008-10-28 at 15:18 -0700, Joshua Drake wrote: Will there be an helper application for setting up and configuring changes in replication. or will it all be done using added SQL commands ? Well, the interface I work on is all SQL commands

[HACKERS] PostgreSQL + Replicator developer meeting 10/28

2008-10-27 Thread Joshua Drake
With the recent open sourcing of Replicator, the team has been trying to come up with ways to ensure an open development process. In that light we have decided to have our first release 1.9 meeting on Freenode. All people interested in participating in a discussion about the upcoming Replicator