Bug#988722: postgresql-common: Upgrading cluster with postgis does not migrate tables using postgis

Sebastiaan Couwenberg sebastic at xs4all.nl
Tue Jun 8 11:57:16 BST 2021


On 6/8/21 12:42 PM, Gilles Filippini wrote:
> But the actual bug will still need to be addressed: postgis requires
> previous runtime to be able to migrate data.

That's an upstream issue, which they don't take very seriously. Some
upstream developers don't like the status quo either, hence the change
in PostGIS 3.0 to drop the minor version to ease this issue somewhat.
But they haven't committed to resolving it entirely.

As I've stated many times now, PostGIS databases need to be recreated
after distribution upgrades or hacks need to be used like they always
have. This is not something new, and not something that will be
addressed in the postgis package.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



More information about the Pkg-grass-devel mailing list