[Django] #32357: Drop support for PostgreSQL 9.6 and PostGIS 2.3.
Django
-------------------------------------+-------------------------------------
Reporter: Mariusz | Owner: Mariusz Felisiak
Felisiak |
Type: | Status: assigned
Cleanup/optimization |
Component: Database | Version: 4.0
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
The end of upstream support for PostgreSQL 9.6 is November 2021.
Therefore, Django 4.0 (released in December 2021) may set PostgreSQL 10 as
the minimum version that it supports. Also drop support for PostGIS 2.3
since it isn't recommended with PostgreSQL 10.
--
Ticket URL: <https://code.djangoproject.com/ticket/32357>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Type: | Felisiak
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* has_patch: 0 => 1
Comment:
[https://github.com/django/django/pull/13894 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/32357#comment:1>
Django
-------------------------------------+-------------------------------------
Type: | Felisiak
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution:
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by David Smith):
Should the policy for removing support be consistent? For example Python
support we are looking ahead to 4.2, should the same arguments (both for
and against) also apply here?
I'm not taking a view here either way, it's just the inconsistency that
I'm challenging.
--
Ticket URL: <https://code.djangoproject.com/ticket/32357#comment:2>
Django
-------------------------------------+-------------------------------------
Type: | Felisiak
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution:
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:2 David Smith]:
> Should the policy for removing support be consistent? For example Python
support we are looking ahead to 4.2, should the same arguments (both for
and against) also apply here?
>
> I'm not taking a view here either way, it's just the inconsistency that
I'm challenging.
We have a special policy about Python version support, in other cases
(e.g. databases) we drop support immediately when they are no longer
supported by creators. You can start a discussion on DevelopersMailingList
if you think we should change it.
--
Ticket URL: <https://code.djangoproject.com/ticket/32357#comment:3>
Django
-------------------------------------+-------------------------------------
Type: | Felisiak
Component: Database layer | Version: 4.0
(models, ORM) |
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"5371342ed66f5ff9feae9dc4586ec43830bbeca6" 5371342e]:
{{{
#!CommitTicketReference repository=""
revision="5371342ed66f5ff9feae9dc4586ec43830bbeca6"
Fixed #32357 -- Dropped support for PostgreSQL 9.6 and PostGIS 2.3.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32357#comment:4>