wiki:UsersWikiPostgreSQLPostGIS

Version 220 (modified by robe, 13 months ago) ( diff )

--

Current best

As of 29th June, 2023 these versions are latest and give you best stable feature coverage.

Obsolete versions can be found at - PostGISObsoleteVersionsMatrix

PostGIS Support Matrix

Versions of PostgreSQL supported by which versions of PostGIS

PostgreSQL versionPostGIS 2.5 EOLPostGIS 3.0PostGIS 3.1PostGIS 3.2PostGIS 3.3 PostGIS 3.4PostGIS 3.5
PostGIS release date 2018/09/23 2019/10/20 2020/12/18 2021/12/18 2022/08/27 2023/08/15 2024/xx/xx
16NoNoNoNoYesYesYes
15NoNoNoYesYesYesYes
14NoNoYesYesYesYesYes
13NoYesYesYesYesYesYes
12YesYesYesYesYesYesNo
11 EOLYesYesYesYesYesNoNo

Versions of PostGIS labeled 'EOL' will no longer receive any micro updates or security patches. If you are running these you should upgrade to the latest version you can.

* Means it currently does or doesn't but may change at release time.

As a general rule, the PostGIS Project Steering committee tries to maintain support of PostGIS for at least two versions of PostgreSQL. We most often support more than 2 PostgreSQL versions, if requirements do not necessitate bumping up requirement without too much effort. We will rarely support more than 5 PostgreSQL versions on any release.

64-bit Windows version support started in PostGIS 2.0.0 (both 9.0 and 9.1)

Versions of GEOS support for PostGIS

The below chart shows which versions of GEOS work with which versions of PostGIS. The none means that you can get that version to work without GEOS, though its not recommended since a lot of functions will not be installed.

For the not recommended, this means that while you can get PostGIS to work with those versions, you'll be missing out on some PostGIS functions. Yes (1) means we assume it works, but don't test it and haven't patched tests to regress cleanly. Some regression tests may fail as newer version give slightly different answers from previous versions.

Yes * - currently works but may not work at release time or fails some regression tests Blank slots means it doesn't work.

Geos VersionPostGIS 2.5 EOLPostGIS 3.0PostGIS 3.1PostGIS 3.2PostGIS 3.3PostGIS 3.4'PostGIS 3.5
3.13Yes(1)Yes(1)Yes(1)YesYesYesYes
3.12Yes(1)Yes(1)Yes(1)YesYesYesYes
3.11Yes(1)Yes(1)Yes(1)YesYes(1)YesYes
3.10Yes(1)Yes(1)YesYesYesYesYes
3.9Yes (1)Yes (1)YesYesYesYesYes
3.8YesYesYesYesYesYesYes
3.7YesYesYesYesYesYesYes
3.6 EOLYesYesYesYesYesYesNo

Versions of Proj support for PostGIS

Yes (1): It works but may have regression failures or not recommended

Yes (2): it works but some features disabled

If a cell is not filled in after, means support stopped for it.

PROJ VersionPostGIS 2.5 EOLPostGIS 3.0PostGIS 3.1PostGIS 3.2PostGIS 3.3PostGIS 3.4PostGIS 3.5
9.1-9.2NoYesYesYesYesYesYes
8.1-8.2NoYesYesYesYesYesYes
7.0-7.2Yes (1)YesYesYesYesYesYes
6.1-6.3YesYesYesYesYesYesNo
6.0NoYesYesYesYesNoNo
5.0-5.2YesYesYesYesYesNoNo

Versions of GDAL support for PostGIS

PostGIS raster functionality (introduced in 2.0) depends on GDAL so to get raster functionality, you'll need to compile with GDAL support and preferably 1.9 or above. Although you can compile PostGIS 2.0 without raster support, you really should rethink that decision, especially if you are a package maintainer (you'll have a lot of pissed off users if you do :)). For PostgreSQL 9.1 extension support, compiling with raster support is ABSOLUTELY required since the postgis extension includes the raster functionality.

* Means it currently does or doesn't but may change at release time.

Yes (1) Assumed to work but we did not test it

Blank - support stopped at this point

GDAL VersionPostGIS 2.4 - 2.5PostGIS 3.0 - 3.3
3.2-3.6Yes (1)Yes
3.0-3.1YesYes (1)
2.0-2.4 EOLYesYes(1)

Packaging status

See UsersWikiPackages

Note: See TracWiki for help on using the wiki.