TheCubicWebBook #153980 bugs in migration from postgres8.1 to postgres8.3 [open]
When migrating from etch to lenny, we have to migration postgres from 8.1 to 8.3 Using pg_dropcluster 8.3 main # this will remove all databases managed by 8.3 pg_upgradecluster -v 8.3 8.1 main gives a bunch of errors which apparently we can safely ignore. There are some missing postgres packages (dependencies ?) - I installed that after the upgradecluster : apt-get -uVf install postgresql-contrib-8.3 postgresql-plpython-8.3 For me python-indexer was not working (python2.4 -> python2.5) so I had to : apt-get -uVf --reinstall install python-indexer For each database had to postgres@:~$ psql databasename databasename=# CREATE LANGUAGE plpythonu; CREATE LANGUAGE databasename=# \q postgres@:~$ cat /usr/share/cubicweb/cubes/jpl/schema/_regproc.sql.postgres | psql databasename CREATE FUNCTION CREATE FUNCTION Finally the appears table was not migrated, had to recreate it before db-rebuild-fti. | |
priority | normal |
---|---|
type | bug |
done in | <not specified> |
load | 0.200 |
load left | 0.200 |
closed by | <not specified> |
similar entities
- PGStaging - setup and maintain your staging environments from your production backups (http://packages.debian.org/sid/pgstaging)
- cubicweb #473794 when an entity type is renamed, physical db index should be renamed as well
- cubicweb #1768109 [migration] add_cube will create missing entities from unrelated cubes
- cubicweb #1113844 Migration script function to reindex a given entity
- TheCubicWebBook #541389 installation from debian package
[see all]
Comments
-
2009/02/26 08:17, written by sthenault
-
2009/03/10 15:30, written by alutz
-
2009/03/11 07:45, written by sthenault
-
2009/11/29 16:29, written by nchauvat
add commentI don't think we can do anything for that except some doc explaining caveats
Doing the install of postgresql-contrib-8.3 postgresql-plpython-8.3 and reinstall of indexer before the pg_upgradecluster clearly shows better results.
You still have to add the relation appears to your databases with
add some tip to the documentation (faq?) and implements #229677, then mark this ticket as done.
#229677 is done.