public inbox for [email protected]
help / color / mirror / Atom feedFrom: Thomas Harold <[email protected]>
To: Albe Laurenz <[email protected]>
To: [email protected] <[email protected]>
Subject: Re: PG replication across DataCenters
Date: Mon, 09 Dec 2013 11:09:21 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <A737B7A37273E048B164557ADEF4A58B17C5ED75@ntex2010i.host.magwien.gv.at>
References: <CAD7Ssm9S__ZQCOq2GEN0G0rrs_4U6aqXiLaX0hh0Ts8JH_LY2w@mail.gmail.com>
<A737B7A37273E048B164557ADEF4A58B17C5ED75@ntex2010i.host.magwien.gv.at>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-general>
On 11/22/2013 5:57 AM, Albe Laurenz wrote:
> Kaushal Shriyan wrote:
>> I have read on the web that Postgresql DB supports replication
>> across data centers. Any real life usecase examples if it has been
>> implemented by anyone.
>
> Well, we replicate a 1 TB database between two locations. It is a
> fairly active OLTP application, but certainly not pushing the limits
> of what PostgreSQL can do in transactions per second.
>
Something that section 25 in the pgsql documentation is not clear about
for hot-standby with WAL log shipping using the built-in streaming:
Can you choose which databases / tables on the master server get
streamed to the hot-standby read-only server at the remote site? If
not, I suspect we'll have to go with either Slony or Bucardo.
--
Sent via pgsql-general mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
view thread (36+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: PG replication across DataCenters
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox