Forums / Install & configuration / failure upgrading 4.0.0 to 4.0.1 (postgresql)
Giovanni Gigante
Thursday 27 November 2008 8:51:30 am
When upgrading Exponential from 4.0.0 to 4.0.1, using the procedure described herehttp://ez.no/doc/ez_publish/upgrading/upgrading_to_4_0/from_4_0_x_to_4_0_y
at step 2 (upgrading the database), I enterpsql -d MYDATABASE -U MYDBUSER < update/database/postgresql/4.0/dbupdate-4.0.0-to-4.0.1.sql
and I get this: UPDATE 1 UPDATE 1 CREATE INDEX CREATE INDEX CREATE INDEX ALTER TABLE ALTER TABLEERROR: column "alias_redirects" contains null values
database is postgresql 8.1.11.
Friday 28 November 2008 8:15:50 am
I <i>think</i> I have found a fix for this problem.
The last lines of the update/database/postgresql/4.0/dbupdate-4.0.0-to-4.0.1.sql script are:
ALTER TABLE ezurlalias_ml ADD COLUMN alias_redirects INT; ALTER TABLE ezurlalias_ml ALTER COLUMN alias_redirects SET default 1; ALTER TABLE ezurlalias_ml ALTER COLUMN alias_redirects SET NOT NULL;
This cannot work, since SET DEFAULT does not apply to existing rows.So it should be:
ALTER TABLE ezurlalias_ml ADD COLUMN alias_redirects INT; ALTER TABLE ezurlalias_ml ALTER COLUMN alias_redirects SET default 1; UPDATE ezurlalias_ml SET alias_redirects=1; ALTER TABLE ezurlalias_ml ALTER COLUMN alias_redirects SET NOT NULL;
...Still the fun (?) is not over. Arriving at step 5 of the upgrade procedure, this is what I get:
$ php extension/ezurlaliasmigration/scripts/migrate.php The number of custom url aliases are: The number of history entries are: Segmentation fault
now I am really stuck...
Kristof Coomans
Friday 28 November 2008 9:38:56 am
Hi Giovanni
This was reported in our issue tracker here: http://issues.ez.no/13681
independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org
Friday 28 November 2008 10:44:12 am
Ok, that's for the first problem. But what about the second one?
The segfault seem to happen at the
$script->shutdown();
line of the script extension/ezurlaliasmigration/scripts/migrate.php
(Running on php 5.2.4)
Saturday 21 March 2009 8:08:06 am
Now I think this segfault is a postgresql bug. For a possible workaround, seehttp://issues.ez.no/IssueView.php?Id=14639&activeItem=1