Repository navigation
DB migration from v2 to v3 failing #8279
|
Edit: Okay, when you see database errors like below, don't use your old database. Create a new one and use the export/import as described in the upgrade guide. But I don't know, why this discussion got locked 🤷♂️ --- initial question --- When starting Wiki.js 3.3.1 Container the first time with a existing DB from 2.5.317 (bare metal) I got an exception at the DB migration check step: Using the same connection values and credentials as before. Running with Podman 5.8.9 on Fedora Cloud. |
Replies: 2 comments 3 replies
|
The error comes from Postgres schemas, not your data, and it also points to a bigger issue: 3.x can't upgrade a 2.x database yet. Why You can confirm it with: SELECT extname, extnamespace::regnamespace AS schema FROM pg_extension;You'll most likely see The bigger issue: 3.x has a guard for this case, What I'd do:
If you really want 3.x in the same database and 2.x is already retired, you can move the extension instead ( It might also be worth an issue so the legacy check looks in |
READ THE DOCS.