From: | Ben <bench(at)silentmedia(dot)com> |
---|---|
To: | Drew Myers <drew(dot)myers(at)innerwireless(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postgres and geographically diverse replication |
Date: | 2007-04-18 20:33:30 |
Message-ID: | Pine.LNX.4.64.0704181325030.27105@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
To answer your question meaningfully, you need to provide more details.
What are you trying to get out of "replication"? High availability? Load
sharing?
On Wed, 18 Apr 2007, Drew Myers wrote:
>
> Hi,
>
> I've been given a task to build a couple of geographically separate
> servers, which are capable of replicating data between each other.
>
> I've surfed through various google results, and most of what I've found
> seems to be a bit dated, so I thought I'd pose my question here, perhaps
> for more detailed and more up-to-date info.
>
> Is this normally done in a push/pull scenario within the postgres
> installations themselves, or is additional software required? What are
> the various replication capabilities?
>
> I apologize for the general nature of my questions, I'm new to postgres
> and to geographically separate replication. Any tips, books, whitepapers
> or other resources you might be able to point me to is most appreciated.
>
> Thanks,
>
> Drew Myers
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Moran | 2007-04-18 20:43:28 | Re: Postgres and geographically diverse replication |
Previous Message | Drew Myers | 2007-04-18 19:55:59 | Postgres and geographically diverse replication |