[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Approaches to maintain clinical data uptime
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] Approaches to maintain clinical data uptime |
Date: |
Sat, 29 Apr 2006 20:26:21 +0200 |
User-agent: |
Mutt/1.5.11+cvs20060403 |
On Sat, Apr 29, 2006 at 09:35:22PM +1000, Tim Churches wrote:
> Have any GNUmeders had any real-life experience with Slony-1? It is hard
> to find any stories, good or bad, about it. We were about to test it to
> implement a hot spare DB for our NetEpi application (which uses PG
> back-end storage), so I read the documentation and realised that Slony
> doesn't replicate schema changes - if the schema changes on the master,
IIRC the newest version does replicate schema changes with
some help: you need to provide some script which does the
changes but Slony will apply them within it's framework so
it stays consistent overall.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
- Re: [Gnumed-devel] Approaches to maintain clinical data uptime, Syan Tan, 2006/04/30
- Re: [Gnumed-devel] Approaches to maintain clinical data uptime, Syan Tan, 2006/04/30
- Re: [Gnumed-devel] Approaches to maintain clinical data uptime, Tim Churches, 2006/04/30
- Re: [Gnumed-devel] Approaches to maintain clinical data uptime, Syan Tan, 2006/04/30
- Re: [Gnumed-devel] Approaches to maintain clinical data uptime, Syan Tan, 2006/04/30
- Re: [Gnumed-devel] Approaches to maintain clinical data uptime, Tim Churches, 2006/04/30
- Re: [Gnumed-devel] Approaches to maintain clinical data uptime, Tim Churches, 2006/04/30