gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] Concurrent connections on the same patient


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Concurrent connections on the same patient
Date: Thu, 28 Jun 2012 22:59:16 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On Thu, Jun 28, 2012 at 10:20:01PM +0200, Slappinjohn wrote:

> >> It would be really helpful if the end result is shareable.
> > 
> > I agree most decidedly !
> 
> This was my plan. For me choosing bucardo is like a proof of concept.
> It's adoptable to nearly every situation (at least most) that could
> occur with a multiple database server setup (not only for GNUmed...)
> 
> Actually it's not as easy-peasy as I thought at the beginning :-(
> (documentation is also improvable, wiki is not up-to-date, man page
> differs to commandline-help...)
> 
> Karsten, the following tables have no primary key (pgadmin agrees! ;-) )
> 
> cfg.cfg_numeric
> cfg.cfg_str_array
> cfg.cfg_string
> 
> if they are needed I/you have to add one and than it should work
> (hopefully). If testing the replication confirms it, I'll post the
> configuration steps.

I have added the attached file to the bootstrapping process
for v18. We cannot simply add this to v17 because that would
change the database fingerprint which the client checks at
startup.

You can, however, still apply it (uncommnt "set
default_transaction_read_only" first) if you are prepared to
always run with --debug and click through the warning.

Karsten
-- 
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

Attachment: v18-cfg-cfg_-static.sql
Description: application/sql


reply via email to

[Prev in Thread] Current Thread [Next in Thread]