peer-to-peer replication with Postgres

From: Mike Christensen <mike(at)kitchenpc(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: peer-to-peer replication with Postgres
Date: 2010-05-08 04:12:46
Message-ID: AANLkTimRaJB9GGp0-0WE9L6DUieqTGsxRNrOizcO6e21@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I'm considering using a cloud hosting solution for my website. It
will probably be either Amazon, Rackspace or Hosting.com. I'm still
comparing. Either way, my site will consist of multiple virtual
server instances that I can create and destroy as needed. Each
virtual machine instance will be self contained, meaning it'll run the
website and its own instance of postgres. The website will only talk
to the local DB instance. However, if I'm running several machine
instances, I want all the databases to keep in sync preferably with as
little lag as possible.

This is not a master/slave replication issue where there's one big DB
that's always up and everything syncs to, this is basically total
peer-to-peer replication where any time data is updated on one server,
an update command gets sent to all the other servers. I would also
have to address the issue when I provision a new virtual server, I'd
have to import the current data into the DB seamlessly.

What's the best way to do this? Looks like something like pgPool
might be what I want, but I haven't looked into it deeply yet.
Thanks!!

Mike

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rick Yorgason 2010-05-08 07:03:42 Database design confusing pg_restore, and misc pg_restore issues
Previous Message hernan gonzalez 2010-05-08 02:30:55 Re: psql weird behaviour with charset encodings