[postgis-devel] [postgis-users] PostGIS 3.3.0 rc1 in about a week

[Regina Obe]

> I went to count things for the upgrade discussion and found one fewer
> installed file for the geocoder.  I don't know if this is a bug or not.
> 
>   share/postgresql/extension/postgis--unpackaged.sql
>   share/postgresql/extension/postgis_raster--unpackaged.sql
>   share/postgresql/extension/postgis_topology--unpackaged.sql
> 
> vs
> 
>   share/postgresql/extension/postgis--3.3.0beta1--${PKGVERSION}.sql
>   share/postgresql/extension/postgis_raster--3.3.0beta1--${PKGVERSION}.sql
>   share/postgresql/extension/postgis_tiger_geocoder--3.3.0beta1--
> ${PKGVERSION}.sql
>   share/postgresql/extension/postgis_topology--3.3.0beta1--
> ${PKGVERSION}.sql
> 
> (The ${PKGVERSION} is just back-substitution of the declared version

It's not a bug.
postgis_tiger_geocoder and address_standardizer are not built using the
utility scripts, so they don't follow the other extensions model completely.
Those unpackaged versions are built by the utility scripts.  I would rather
postgis_tiger_geocoder and address_standardizer not have those scripts.
Those were mostly useful for unraveling postgis and postgis_raster (when
jumping from < 3.0) from each other as I recall.  Most people should just be
using extensions, so there is no need for these.  If they per chance were
using the sql files, they can always convert by dropping the tiger schema
entirely and the tiger_data schema.  It's a lot of data, but those have to
be reloaded every year to stay current anyway.

I notice postgis_sfcgal and address_standardizer are completely missing from
your list.  I assume you don't package those?

Thanks,
Regina