| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Iñigo Martinez Lasala <imartinez(at)vectorsf(dot)com> |
| Cc: | Renato Oliveira <renato(dot)oliveira(at)grant(dot)co(dot)uk>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Migrate postgres to newer hardware |
| Date: | 2010-04-02 16:45:56 |
| Message-ID: | z2zdcc563d11004020945uf58e8329h4c8b189838282448@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Fri, Apr 2, 2010 at 1:58 AM, Iñigo Martinez Lasala
<imartinez(at)vectorsf(dot)com> wrote:
> I've never worked with Bucardo and Londiste, so I cannot give you any hint
> about it.
> With slony it's not necessary to restore all database prior staring sync
> process. You only have to restore your schema but not data. Slony will keep
> them synced with source server.
>
> Anyway, if you plan to migrate to 8.4 there are some issues with slony. For
> 8.3 and higher, you will go with slony 2.X. For 8.2 with slony 1.X
> I'm not sure if Slony 1.x is compatible with Postgres >= 8.3, but I'm sure
> slony 2.x is not backwards compatible.
slony 1.2.20 is definitely compatible with pg 8.4 and 8.5/9.0
according to the release notes. Not sure if 2.x is considered
production ready. It certainly wasn't last fall.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gnanakumar | 2010-04-03 04:53:25 | Re: Database clone stuck in the middle |
| Previous Message | Tom Lane | 2010-04-02 14:16:56 | Re: Database clone stuck in the middle |