[Django] #23108: Drop support for PostgreSQL 8.4/PostGIS 1.3, 1.4

Django

unread,

Jul 26, 2014, 4:55:22 PM7/26/14

to django-...@googlegroups.com

#23108: Drop support for PostgreSQL 8.4/PostGIS 1.3, 1.4
-------------------------------------+-------------------------------------
Reporter: timo | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: Database | Keywords:
layer (models, ORM) | Has patch: 1
Severity: Normal | Needs tests: 0
Triage Stage: Accepted | Easy pickings: 0
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
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.

--
Ticket URL: <https://code.djangoproject.com/ticket/23108>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,

Jul 27, 2014, 7:58:08 AM7/27/14

to django-...@googlegroups.com

#23108: Drop support for PostgreSQL 8.4/PostGIS 1.3, 1.4
-------------------------------------+-------------------------------------
Reporter: timo | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master

Comment (by abraham.martin):

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?

--
Ticket URL: <https://code.djangoproject.com/ticket/23108#comment:1>

Django

unread,

Jul 27, 2014, 11:15:52 AM7/27/14

to django-...@googlegroups.com

#23108: Drop support for PostgreSQL 8.4/PostGIS 1.3, 1.4
-------------------------------------+-------------------------------------

Reporter: timo | Owner: timo
Type: | Status: assigned
Cleanup/optimization | Version: master

Component: Database layer | Resolution:
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0

Keywords: | Patch needs improvement: 1

Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------

Changes (by timo):

* owner: nobody => timo
* needs_better_patch: 0 => 1
* status: new => assigned

Comment:

Sorry, forget to link the [https://github.com/django/django/pull/2981 PR].
There are still a couple test failures I need to fix.

--
Ticket URL: <https://code.djangoproject.com/ticket/23108#comment:2>

Django

unread,

Jul 28, 2014, 6:57:19 AM7/28/14

to django-...@googlegroups.com

#23108: Drop support for PostgreSQL 8.4/PostGIS 1.3, 1.4
-------------------------------------+-------------------------------------

Reporter: timo | Owner: timo
Type: | Status: assigned
Cleanup/optimization | Version: master

Comment (by jgoclawski):

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.

--
Ticket URL: <https://code.djangoproject.com/ticket/23108#comment:3>

Django

unread,

Jul 28, 2014, 8:45:31 AM7/28/14

to django-...@googlegroups.com

#23108: Drop support for PostgreSQL 8.4/PostGIS 1.3, 1.4
-------------------------------------+-------------------------------------

Reporter: timo | Owner: timo
Type: | Status: assigned
Cleanup/optimization | Version: master

Component: Database layer | Resolution:
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0

Keywords: | Patch needs improvement: 0

Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------

Changes (by timo):

* needs_better_patch: 1 => 0

Comment:

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.

--
Ticket URL: <https://code.djangoproject.com/ticket/23108#comment:4>

Django

unread,

Aug 1, 2014, 10:21:01 AM8/1/14

to django-...@googlegroups.com

#23108: Drop support for PostgreSQL 8.4/PostGIS 1.3, 1.4
-------------------------------------+-------------------------------------

* stage: Accepted => Ready for checkin

--
Ticket URL: <https://code.djangoproject.com/ticket/23108#comment:5>

Django

unread,

Aug 1, 2014, 10:26:59 AM8/1/14

to django-...@googlegroups.com

#23108: Drop support for PostgreSQL 8.4/PostGIS 1.3, 1.4
-------------------------------------+-------------------------------------

Reporter: timo | Owner: timo
Type: | Status: closed
Cleanup/optimization | Version: master
Component: Database layer | Resolution: fixed

Changes (by Tim Graham <timograham@…>):

* status: assigned => closed
* resolution: => fixed

Comment:

In [changeset:"a9bdce7e5503a450c2c291fb2cb1e2097617ba75"]:
{{{
#!CommitTicketReference repository=""
revision="a9bdce7e5503a450c2c291fb2cb1e2097617ba75"
Fixed #23108 -- Dropped support for PostgreSQL 8.4 & PostGIS 1.3, 1.4.

Thanks Claude Paroz for the review.
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/23108#comment:6>

Django

unread,

Aug 1, 2014, 10:54:42 AM8/1/14

to django-...@googlegroups.com

#23108: Drop support for PostgreSQL 8.4/PostGIS 1.3, 1.4
-------------------------------------+-------------------------------------

Reporter: timo | Owner: timo
Type: | Status: closed
Cleanup/optimization | Version: master

Comment (by Tim Graham <timograham@…>):

In [changeset:"1a31d9ef913f954c26a4837b1ffb568ced21ff05"]:
{{{
#!CommitTicketReference repository=""
revision="1a31d9ef913f954c26a4837b1ffb568ced21ff05"
Removed some PostGIS 1.4 notes in the docs (refs #23108).
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/23108#comment:7>

Reply all

Reply to author

Forward