| From: | Gabriele Bartolini <gabriele(dot)bartolini(at)2ndQuadrant(dot)it> |
|---|---|
| To: | CS DBA <cs_dba(at)consistentstate(dot)com> |
| Cc: | "Rangi, Jai" <jrangi(at)automotive(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Postgres Replication Options |
| Date: | 2011-02-10 13:56:05 |
| Message-ID: | 4D53EE75.9070007@2ndQuadrant.it |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(dot)bartolini(at)2ndQuadrant(dot)it | www.2ndQuadrant.it
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bernhard Schrader | 2011-02-10 16:56:58 | LC_COLLATE and pg_upgrade |
| Previous Message | Marc Mamin | 2011-02-10 10:54:01 | FILLFACTOR Tuning |