Re: WAL and master multi-slave replication

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Eduardo Morras <emorras(at)s21sec(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: WAL and master multi-slave replication
Date: 2009-06-24 18:16:33
Message-ID: dcc563d10906241116m62caa1f2hf14cb05a4a6e71bb@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Jun 24, 2009 at 11:51 AM, Alvaro
Herrera<alvherre(at)commandprompt(dot)com> wrote:
> Eduardo Morras escribió:
>> At 19:25 24/06/2009, you wrote:
>>> On Wed, Jun 24, 2009 at 11:22 AM, Eduardo Morras<emorras(at)s21sec(dot)com> wrote:
>>> > Yes, there will be 3 masters recolleting data (doing updates, inserts and
>>> > deletes) for now and 5 slaves where we will do the searches. The
>>> slaves must
>>> > have all the data recollected by the 3 masters and the system must be
>>> easily
>>> > upgradable, adding new masters and new slaves.
>>>
>>> You know you can't push WAL files from > 1 server into a slave, right?
>>
>> No, i didn't know that.
>
> I guess you don't know either that you can't query a slave while it is
> on recovery (so it's only a "warm" standby, not hot).  And if you bring
> it up you can't afterwards continue applying more segments later.

I think the OP's needs might be better met by slony or londiste and
some views over the top of a bunch of tables than using PITR.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Madison Kelly 2009-06-24 18:16:44 Re: Return LEFT JOINed tables when one has no matching column
Previous Message Alvaro Herrera 2009-06-24 17:51:12 Re: WAL and master multi-slave replication