Summary: | postgresql-server-8.4.2-r1 does not start | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dmitry Grigoriev <dimgel> |
Component: | [OLD] Server | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | alunduil, casta |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dmitry Grigoriev
2010-01-08 03:48:32 UTC
What if you zap the service first: /etc/init.d/postgresql-8.4 zap? Does it allow you to start the service after that? Same problem here : seems that 8.4.2-r1 enables HAVE_INT64_TIMESTAMP wheras previous version did not (see your postmaster.log) So you need to dump your data (with the old version), then restore after upgrade ! Sorry, I forget this : you should have see the "pg_legacytimestamp" USE flag Enable it to have a working DB without dump/restore ;) "zap" did not not help. What helped: 1. downgrade to 8.4.2 2. # pg_dumpall -Upostgres > postgresql-8.4.2.sql 3. re-upgrade to 8.4.2-r1 4. # cd /var/lib/postgresql; mv 8.4 8.4.2 5. # emerge --config =dev-db/postgresql-server-8.4.2-r1 6. # /etc/init.d/postgresql-8.4 start 7. # psql -Upostgres -f postgresql-8.4.2.sql postgres Guillaume Castagnino, thank you. I'm closing this ticket. |