Re: Data Replication

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: Tim Uckun <timuckun(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Data Replication
Date: 2008-12-11 06:13:12
Message-ID: 1228975992.10622.0.camel@jd-laptop.pragmaticzealot.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 2008-12-10 at 21:39 -0700, Scott Marlowe wrote:
> On Wed, Dec 10, 2008 at 8:43 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> > On Wed, 2008-12-10 at 20:41 -0700, Scott Marlowe wrote:
> >> On Wed, Dec 10, 2008 at 7:40 PM, Tim Uckun <timuckun(at)gmail(dot)com> wrote:
> >
> >> Log shipping doesn't really lends itself to switching back and forth
> >> between masters and slaves.
> >
> > Really? It seems to me that you can make a base backup just as fast as
> > you can sync from slony (or replicator or whatever).
>
> sorry if my post wasn't clear. slony's not really any better. I don't
> think that there's any replication for pgsql that's easy to do that
> in. Is there?

No probably not. I mean they are all pretty easy (especially log
shipping) but it is definitely true they are slow, depending on the size
of the database.

Joshua D. Drake

>
--
PostgreSQL
Consulting, Development, Support, Training
503-667-4564 - http://www.commandprompt.com/
The PostgreSQL Company, serving since 1997

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Maximilian Tyrtania 2008-12-11 06:32:19 Re: tcp_keepalives_idle setting
Previous Message Adam Rich 2008-12-11 05:54:33 Re: Multi-table CHECK constraint