On 04/28/2017 04:01 PM, Sebastiaan Couwenberg wrote: > On 04/26/2017 01:02 PM, Bas Couwenberg wrote: >> It's probably sufficient to fix the case of the constraints as per the >> attached patch. I've haven't tested this (yet), as I don't know who to >> reproduce the issue with piuparts. > > The patch is not the solution. Because the problem is not the case of > the constraint. > > The squeeze version of icinga doesn't create a named constraint, this > was changed in the wheezy version. The database upgrade scripts for the > various versions don't change the constraints though. > > Adding "IF EXISTS" will likely help to address the SQL error (per the > attached patch), but will not fix the upstream issue as the unnamed > UNIQUE constraints will still be present.
Also removing the automatically named constraints if they exists is probably sufficient. I've updated the proposed patch once again. Markus, what do you think? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
pgsql-upgrade-1.13.0.patch
Description: application/pgp-encrypted
