[Django] #33885: Drop automatic PostGIS extension creation on PostGIS backend

[Django]

#33885: Drop automatic PostGIS extension creation on PostGIS backend
-------------------------------------+-------------------------------------
Reporter: Johannes | Owner: nobody
Maron |
Type: | Status: new
Cleanup/optimization |
Component: GIS | Version: 4.0
Severity: Normal | Keywords:
Triage Stage: | fly.a...@gmail.com
Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
-------------------------------------+-------------------------------------
Thanks to our friends at Heroku, we currently can't execute `create
extension` without our database throwing an error.

That made us aware of the fact, that the database wrapper for PostGIS
execute a SQL statement every time it prepares the database.

That behavior seems inconsistent with how any other PG extension works.
Usually, those have to be initialized in a migration explicitly. There has
been a debate in the past, if that statement can do any harm, but clearly
Heroku has proven it can. Therefore, I would suggest deprecating this
behavior and schedule it for deletion in Django 5.

Superseeds #28975

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

[Django]

#33885: Drop automatic PostGIS extension creation on PostGIS backend
-------------------------------------+-------------------------------------

Reporter: Johannes Maron | Owner: nobody

Type: | Status: new
Cleanup/optimization |
Component: GIS | Version: 4.0

Severity: Normal | Resolution:
Keywords: | Triage Stage:

| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Johannes Maron):

* keywords: fly.a...@gmail.com =>

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

[Django]

#33885: Drop automatic PostGIS extension creation on PostGIS backend
-------------------------------------+-------------------------------------
Reporter: Johannes Maron | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: GIS | Version: 4.0
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by amureki):

* cc: amureki (added)

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

[Django]

#33885: Drop automatic PostGIS extension creation on PostGIS backend
-------------------------------------+-------------------------------------
Reporter: Johannes Maron | Owner: nobody

Type: | Status: closed

Cleanup/optimization |
Component: GIS | Version: 4.0

Severity: Normal | Resolution: duplicate

Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):

* status: new => closed
* resolution: => duplicate
* easy: 1 => 0

Comment:

Thanks for the reports, It's definitely a duplicate of #28975 (that we can
reopen, if needed).

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

[Django]

#33885: Drop automatic PostGIS extension creation on PostGIS backend
-------------------------------------+-------------------------------------
Reporter: Johannes Maron | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: GIS | Version: 4.0
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Johannes Maron):

Replying to [comment:3 Mariusz Felisiak]:

> Thanks for the reports, It's definitely a duplicate of #28975 (that we
can reopen, if needed).

Thanks for the swift triage. I didn't feel comfortable to reopen it, since
it was about skipping it in Python and I would rather not make the call at
all. But I can reopen it and make my case without changing the ticket
description.

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