#23108 closed Cleanup/optimization (fixed)
Drop support for PostgreSQL 8.4/PostGIS 1.3, 1.4
| Reported by: | Tim Graham | Owned by: | Tim Graham |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The end of upstream support periods was reached in July 2014 for PostgreSQL 8.4. As a consequence, Django 1.8 may set 9.0 as the minimum PostgreSQL version it officially supports.
This also includes dropping support for PostGIS 1.3 and 1.4 as these versions are not supported on versions of PostgreSQL later than 8.4.
Change History (7)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
| Owner: | changed from to |
|---|---|
| Patch needs improvement: | set |
| Status: | new → assigned |
Sorry, forget to link the PR. There are still a couple test failures I need to fix.
comment:3 by , 10 years ago
And what about support for PostGIS 1.5?
According to https://code.djangoproject.com/ticket/23085 PostGIS 1.5 (migrations) are not supported in Django 1.7. But according to this: http://trac.osgeo.org/postgis/wiki/UsersWikiPostgreSQLPostGIS PostgreSQL 9.0 (and up to 9.2) supports PostGIS 1.5.
I feel we have an inconsistency here.
comment:4 by , 10 years ago
| Patch needs improvement: | unset |
|---|
You can still use Django 1.7 without migrations (and thus PostGIS 1.5).
I've fixed the test failures so the patch should be ready for review.
comment:5 by , 10 years ago
| Triage Stage: | Accepted → Ready for checkin |
|---|
comment:6 by , 10 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
I found some version checks to perform one or other action but none that checks the version number and raises an exception if it is not supported. It is suppose to be like this?