Summary: | dev-db/postgresql-13.1 Migration as documented needs update and doesn't work if PostGIS is involved | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jeff Hubbs <jeffrey.hubbs> |
Component: | Current packages | Assignee: | PgSQL Bugs <pgsql-bugs> |
Status: | RESOLVED CANTFIX | ||
Severity: | major | CC: | jeffrey.hubbs, jstein |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jeff Hubbs
2021-01-04 23:26:53 UTC
Something else I noticed: # psql --username=postgres --dbname=deleteme -c "CREATE EXTENSION postgis;" ERROR: could not open extension control file "/usr/share/postgresql-13/extension/postgis.control": No such file or directory It's missing but present under /usr/share/postgresql-12/extension. It's as though the postgis installation just doesn't know anything about postgresql-13. I've found out more. It turns out that no version of postgis in portage, not even the ones that are still masked, are postgresql-13-ready. it seems that if you are using postgis on Gentoo, you have no choice but to mask out anything higher than postgresql-12.5 for the time being. Documentation-wise, this bridge is out. Well, the documentation mostly worked for me as is. There is a note about the /usr/lib. I've just migrated a system yesterday using the instructions, and they mostly worked for me. There is a note about the /usr/lib on multilib systems. So, I needed to adjust for that. It does guide the reader that you need to if there's a hiccup, to read the log as you did. It should perhaps now mention updating the POSTGRES_TARGETS. If you think there is a way to make it clearer, you are welcome to edit the documentation. It's a wiki. The worse that can happen to an edit done in earnest is for it to be reverted. Also, the appropriate location to discuss edits, if you're uncertain about an edit, or even to start discussing trouble spots you have is at: https://wiki.gentoo.org/wiki/Talk:PostgreSQL/QuickStart Thirteen months on and the situation is the same. I just revisited this problem on the same server and there hasn't been a new ebuild for PostgreSQL 13 in the interim although postgis has advanced from 2.5 to 3.1.3. Here is what happens now; it's slightly changed from before: sh-5.1$ pg_upgrade -U postgres -d /var/lib/postgresql/12/data -D /var/lib/postgresql/13/data -b /usr/lib64/postgresql-12/bin -B /usr/lib64/postgresql-13/bin Performing Consistency Checks ----------------------------- Checking cluster versions This utility can only upgrade to PostgreSQL version 12. Failure, exiting sh-5.1$ pg_upgrade13 -U postgres -d /var/lib/postgresql/12/data -D /var/lib/postgresql/13/data -b /usr/lib64/postgresql-12/bin -B /usr/lib64/postgresql-13/bin Performing Consistency Checks ----------------------------- Checking cluster versions ok Checking database user is the install user ok Checking database connection settings ok Checking for prepared transactions ok Checking for system-defined composite types in user tables ok Checking for reg* data types in user tables ok Checking for contrib/isn with bigint-passing mismatch ok Creating dump of global objects ok Creating dump of database schemas commercial_bldgs *failure* Consult the last few lines of "pg_upgrade_dump_17993.log" for the probable cause of the failure. Failure, exiting That log file says: command: "/usr/lib64/postgresql-13/bin/pg_dump" --host /var/lib/postgresql --port 50432 --userna me postgres --schema-only --quote-all-identifiers --binary-upgrade --format=custom --file="pg_u pgrade_dump_17993.custom" 'dbname=commercial_bldgs' >> "pg_upgrade_dump_17993.log" 2>&1 pg_dump: error: query failed: ERROR: could not access file "$libdir/postgis-2.5": No such file or directory PostgreSQL and PostGIS have both been reemerged with POSTGRES_TARGETS="postgres12 postgres13" in make.conf. Note that I am using pg_upgrade13 now. For some reason the pg_update process is still looking for $libdir/postgis-2.5 whem it seems like it should be looking for postgis-3. |