On 2014-08-07 at 12:33:27 [+0200], Andrew Lindesay <apl@xxxxxxxxxxxxxx> wrote:
Not sure if you caught that I had pushed a patch for this database
migration issue; so it should be ready for another re-attempt at deployment.
Yep, I did catch that and I've just checked again, but git pull isn't
fetching anything new.
The error message changed inbetween tries (I think it failed when trying to
alter a column in the prominence table to be not null at first and now it
fails when trying to create the prominence_id foreign index), so something
has changed, apparently just something else is missing.
If you prefer, we can just as well try with postgres-9.3. Just say so and I
will try to upgrade postgres to 9.3.5.
cheers,
Oliver
