PostGIS 3.2.0beta3 Released
The PostGIS Team is pleased to release the third beta of the upcoming PostGIS 3.2.0 release.
Best served with PostgreSQL 14. This version of PostGIS can utilize the faster GiST building support API introduced in PostgreSQL 14. If compiled with recently released GEOS 3.10.1 you can take advantage of improvements in ST_MakeValid and numerous speed improvements. This release also includes many additional functions and improvements for postgis
, postgis_raster
and postgis_topology
extensions and a new input/export format FlatGeobuf.
3.2.0beta3
This release supports PostgreSQL 9.6-14, GEOS 3.6 and higher, and proj 4.9 and higher.
- source download
- NEWS
- PDF docs en
- html doc download
- html online en
- epub doc download
Details of this release can be found in NEWS file: https://git.osgeo.org/gitea/postgis/postgis/src/tag/3.2.0beta3/NEWS and is also included in the source tar ball.
If you come across any issues, feel free to report via our ticket tracker or mailing list with details as described in SUPPORT
Changes since PostGIS 3.2.0beta2 release are listed below.
Due to some query performance degradation with the new fast index build that requires PG14, we have decided to disable the feature by default until we get more user testing as to the true impact of real-world queries.
If you are running PG14+, you can reenable it by doing
ALTER OPERATOR FAMILY gist_geometry_ops_2d
USING gist
ADD FUNCTION 11 (geometry)
geometry_gist_sortsupport_2d (internal);
To revert the change:
ALTER OPERATOR FAMILY gist_geometry_ops_2d
USING gist
DROP FUNCTION 11 (geometry);
and then reindex your gist indexes.
View all closed tickets for 3.2.0beta3.
Bug Fixes and Breaking Changes
- #5028, ST_AsFlatGeobuf crashes on mixed geometry input (Björn Harrtell)
- #5029, ST_AsFlatGeobuf indexed output corruption (Björn Harrtell)
- #5014, Crash on ST_TableFromFlatGeobuf (Björn Harrtell)
- Rename ST_TableFromFlatGeobuf to ST_FromFlatGeobufToTable (Björn Harrtell)
- PG14 fast index building disabled by default. (Paul Ramsey)
After installing the binaries or after running pg_upgrade:
For PostGIS 3.1, 3.0, 2.5 Do the below which will upgrade all your postgis extensions.
SELECT postgis_extensions_upgrade();