[Dbconfig-common-devel] Difficult/partial upgrade

Karsten Hilbert Karsten.Hilbert at gmx.net
Mon Feb 21 07:07:41 UTC 2011


On Sun, Feb 20, 2011 at 10:01:18PM +0100, Vincent Bernat wrote:

> > Hm, why not simply DROP the offending INDEXe before
> > (re)-creating them and ignoring errors on the drop ?
> 
> > After all, the worst that might happen is that while the
> > INDEXs are briefly unavailable some queries would run slower
> > than normal ...
> 
> Unfortunately, I have  to deal with partial upgrades as  well. If a user
> already upgraded to  0.5-1 and had a problems  with indexes, some tables
> may not have been created.

Ugh. I see.

That is why GNUmed checksums the schema before and after upgrade.

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



More information about the Dbconfig-common-devel mailing list