pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedPostgres Replication Options
5+ messages / 4 participants
[nested] [flat]
* Postgres Replication Options
@ 2011-02-09 00:34 Rangi, Jai <jrangi@automotive.com>
2011-02-09 01:39 ` Re: Postgres Replication Options Rosser Schwarz <rosser.schwarz@gmail.com>
2011-02-09 07:11 ` Re: Postgres Replication Options Gabriele Bartolini <gabriele.bartolini@2ndQuadrant.it>
0 siblings, 2 replies; 5+ messages in thread
From: Rangi, Jai @ 2011-02-09 00:34 UTC (permalink / raw)
To: pgsql-admin
Hello,
I am looking for a replication solution for PG 9.x. Idea is to have one
master replication server and multiple (around 20) slave servers read
only. I see PG 9 has inbuilt Streaming replication. Is this the best
replication solution. How about slony? Which option will keep the slave
nodes in closest sync to master and which is more stable.
I found some stuff on google, but looking for some guidance from people
who has "been there and done that".
-JP
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Postgres Replication Options
2011-02-09 00:34 Postgres Replication Options Rangi, Jai <jrangi@automotive.com>
@ 2011-02-09 01:39 ` Rosser Schwarz <rosser.schwarz@gmail.com>
1 sibling, 0 replies; 5+ messages in thread
From: Rosser Schwarz @ 2011-02-09 01:39 UTC (permalink / raw)
To: Rangi, Jai <jrangi@automotive.com>; +Cc: pgsql-admin
On Tue, Feb 8, 2011 at 5:34 PM, Rangi, Jai <jrangi@automotive.com> wrote:
> I am looking for a replication solution for PG 9.x. Idea is to have one
> master replication server and multiple (around 20) slave servers read only.
I know (anecdotally) of at least one organization that's using Bucardo
[1] to synchronize many more machines than that. I've used it to
manage eight to ten slaves, simultaneously with master-master
replication without significant issue, and with a replication lag
typically in the low single-digit seconds, at the outside.
In order to reduce replication overhead and keep things performant
with as many slaves as you're talking about, you might want to use
"cascaded" slaves, where the R/W master updates a subset of the
slaves, which then propagate the changes to slaves of their own. Look
at the documentation for "makedelta" to enable cascading slave tiers.
rls
[1] http://bucardo.org
--
:wq
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Postgres Replication Options
2011-02-09 00:34 Postgres Replication Options Rangi, Jai <jrangi@automotive.com>
@ 2011-02-09 07:11 ` Gabriele Bartolini <gabriele.bartolini@2ndQuadrant.it>
2011-02-09 16:53 ` Re: Postgres Replication Options CS DBA <cs_dba@consistentstate.com>
1 sibling, 1 reply; 5+ messages in thread
From: Gabriele Bartolini @ 2011-02-09 07:11 UTC (permalink / raw)
To: Rangi, Jai <jrangi@automotive.com>; +Cc: pgsql-admin
Hi,
Il 09/02/11 01:34, Rangi, Jai ha scritto:
>
> Hello,
>
> I am looking for a replication solution for PG 9.x. Idea is to have
> one master replication server and multiple (around 20) slave servers
> read only. I see PG 9 has inbuilt Streaming replication. Is this the
> best replication solution. How about slony? Which option will keep the
> slave nodes in closest sync to master and which is more stable.
>
With PostgreSQL 9.0 in terms of builtin replication you can take
advantage of Hot Standby based on either WAL shipping or on Streaming
Replication.I would personally stick with builtin solutions if you plan
to have full replicas of your databases, even in terms of maintenance
and upgrades later on (in the long term). Some tools, including
replication manager (repmgr) are coming out in order to manage HA
clusters (for more info:
http://blog.2ndquadrant.com/en/2011/01/easier-postgresql-90-clusters.html).
Cheers,
Gabriele
--
Gabriele Bartolini - 2ndQuadrant Italia
PostgreSQL Training, Services and Support
gabriele.bartolini@2ndQuadrant.it | www.2ndQuadrant.it
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Postgres Replication Options
2011-02-09 00:34 Postgres Replication Options Rangi, Jai <jrangi@automotive.com>
2011-02-09 07:11 ` Re: Postgres Replication Options Gabriele Bartolini <gabriele.bartolini@2ndQuadrant.it>
@ 2011-02-09 16:53 ` CS DBA <cs_dba@consistentstate.com>
2011-02-10 13:56 ` Re: Postgres Replication Options Gabriele Bartolini <gabriele.bartolini@2ndQuadrant.it>
0 siblings, 1 reply; 5+ messages in thread
From: CS DBA @ 2011-02-09 16:53 UTC (permalink / raw)
To: Gabriele Bartolini <gabriele.bartolini@2ndQuadrant.it>; +Cc: Rangi, Jai <jrangi@automotive.com>; pgsql-admin
One of the main considerations per Hot Standby vs SLONY is replication
scope. With Hot Standby you get everything that occurs in the cluster,
across all databases. With SLONY you are limited to at most a single
database per "SLONY Cluster", and you can define replication sets which
only contain a sub-set of the tables in the database. So, IMHO I'd go
with Hot Standby if I wanted to replicate the full cluster and SLONY if
I wanted to "slice & dice" tables and target slaves (i.e. replicate all
tables for a single db to slave 1, only 50 tables to slave 2, etc...)
--hope this helps
/Kevin
> Hi,
>
> Il 09/02/11 01:34, Rangi, Jai ha scritto:
>>
>> Hello,
>>
>> I am looking for a replication solution for PG 9.x. Idea is to have
>> one master replication server and multiple (around 20) slave servers
>> read only. I see PG 9 has inbuilt Streaming replication. Is this the
>> best replication solution. How about slony? Which option will keep
>> the slave nodes in closest sync to master and which is more stable.
>>
> With PostgreSQL 9.0 in terms of builtin replication you can take
> advantage of Hot Standby based on either WAL shipping or on Streaming
> Replication.I would personally stick with builtin solutions if you
> plan to have full replicas of your databases, even in terms of
> maintenance and upgrades later on (in the long term). Some tools,
> including replication manager (repmgr) are coming out in order to
> manage HA clusters (for more info:
> http://blog.2ndquadrant.com/en/2011/01/easier-postgresql-90-clusters.html).
>
> Cheers,
> Gabriele
> --
> Gabriele Bartolini - 2ndQuadrant Italia
> PostgreSQL Training, Services and Support
> gabriele.bartolini@2ndQuadrant.it |www.2ndQuadrant.it
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Postgres Replication Options
2011-02-09 00:34 Postgres Replication Options Rangi, Jai <jrangi@automotive.com>
2011-02-09 07:11 ` Re: Postgres Replication Options Gabriele Bartolini <gabriele.bartolini@2ndQuadrant.it>
2011-02-09 16:53 ` Re: Postgres Replication Options CS DBA <cs_dba@consistentstate.com>
@ 2011-02-10 13:56 ` Gabriele Bartolini <gabriele.bartolini@2ndQuadrant.it>
0 siblings, 0 replies; 5+ messages in thread
From: Gabriele Bartolini @ 2011-02-10 13:56 UTC (permalink / raw)
To: CS DBA <cs_dba@consistentstate.com>; +Cc: Rangi, Jai <jrangi@automotive.com>; pgsql-admin
Hi,
Il 09/02/11 17:53, CS DBA ha scritto:
> One of the main considerations per Hot Standby vs SLONY is replication
> scope. With Hot Standby you get everything that occurs in the cluster,
> across all databases.
Yep, I agree with you Kevin regarding the replication scope. I assumed
that Jai was looking for a full replica of the server.
> database. So, IMHO I'd go with Hot Standby if I wanted to replicate
> the full cluster and SLONY if I wanted to "slice & dice" tables and
> target slaves (i.e. replicate all tables for a single db to slave 1,
> only 50 tables to slave 2, etc...)
If you are looking for table level replication, I suggest also too look
at Londiste and Skytools.
Ciao,
Gabriele
--
Gabriele Bartolini - 2ndQuadrant Italia
PostgreSQL Training, Services and Support
gabriele.bartolini@2ndQuadrant.it | www.2ndQuadrant.it
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2011-02-10 13:56 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2011-02-09 00:34 Postgres Replication Options Rangi, Jai <jrangi@automotive.com>
2011-02-09 01:39 ` Rosser Schwarz <rosser.schwarz@gmail.com>
2011-02-09 07:11 ` Gabriele Bartolini <gabriele.bartolini@2ndQuadrant.it>
2011-02-09 16:53 ` CS DBA <cs_dba@consistentstate.com>
2011-02-10 13:56 ` Gabriele Bartolini <gabriele.bartolini@2ndQuadrant.it>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox