Changes between Initial Version and Version 1 of Ticket #4979, comment 6


Ignore:
Timestamp:
08/22/21 14:13:11 (3 years ago)
Author:
robe

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #4979, comment 6

    initial v1  
    11We have no contol over what packagers do. I think most no longer remove old releases cause then it would be difficult for people to pg_upgrade from say 2.5 to 3 or 3.1. Note that in the case of pg_upgrade, which many people use these days, both a 2.5 and 3. lib file must exist in the PG12 if you are say upgrading from PG11 to PG12.
    22
    3 I'll test on windows to make sure it's not an issue there, but I doubt it is because at least as far as windows is concerned I statically include liblwgeom in PostGIS 2.5, 2.4 with one of the reasons being for this kind of thing.  Around 3.0/3.1 I we made this the official thing by not exporting liblwgeom anymore.  Before debian would have a patch to undo this and then we saw these kinds of issues with liblwgeom from a previous release latching on to a newer PostGIS.
     3I'll test on windows to make sure it's not an issue there, but I doubt it is because at least as far as windows is concerned I statically include liblwgeom in PostGIS 2.5, 2.4 with one of the reasons being for this kind of thing.  Around 3.0/3.1 we made this the official thing by not exporting liblwgeom anymore.  Before debian would have a patch to undo this and then we saw these kinds of issues with liblwgeom from a previous release latching on to a newer PostGIS.