Updating to the actual Postgres 17 version is more than just using pgupgrade.
pgupgrade is not problem for yus and migel, but oddb.org still has a lot of references to oid, which is no longer supported under postgres 12 and later, see releas notes 12.
We must answer the following questions:
- do we have to rename oid to another name?
- can we replace oid by odba_id?
- how can we migrate (maybe even dumping the whole to yaml and reloading in empty database). This could eliminate cruft we have in the database
Updating to the actual Postgres 17 version is more than just using pgupgrade.
pgupgrade is not problem for yus and migel, but oddb.org still has a lot of references to oid, which is no longer supported under postgres 12 and later, see releas notes 12.
We must answer the following questions: