[Django] #35324: Postgres Extensions Not Available

[Django]

#35324: Postgres Extensions Not Available
--------------------------------------------+------------------------
Reporter: FredAtNeo | Owner: (none)
Type: Bug | Status: new
Component: contrib.postgres | Version: 5.0
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
--------------------------------------------+------------------------
When using a system like django-tenants many extensions installed fail to
be found on use. The solution is to install the extensions in pg_catalog
so they are always in the search path in postgres.
--
Ticket URL: <https://code.djangoproject.com/ticket/35324>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#35324: Postgres Extensions Not Available

----------------------------------+--------------------------------------
Reporter: FredAtNeo | Owner: FredAtNeo
Type: Bug | Status: assigned
Component: contrib.postgres | Version: 5.0
Severity: Normal | Resolution:

Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0

----------------------------------+--------------------------------------
Changes (by FredAtNeo):

* owner: (none) => FredAtNeo
* status: new => assigned

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

[Django]

#35324: Postgres Extensions Not Available

----------------------------------+----------------------------------------
Reporter: Fred Lamming | Owner: Fred Lamming
Type: Bug | Status: closed
Component: contrib.postgres | Version: 5.0
Severity: Normal | Resolution: invalid
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 Natalia Bidart):

* has_patch: 1 => 0
* resolution: => invalid
* status: assigned => closed

Comment:

Hello Fred, thank you for your report.

Could you please explain how Django (core) is at fault here? From your
description, this seems like an issue in django-tenants and it would be
best if you file and solve the issue there.

I'll be closing this ticket as invalid following the
[https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
tickets/#closing-tickets ticket triaging process]. If, after debugging,
you find out that this is indeed a bug in Django, please re-open with the
specific details and please be sure to include a small Django project to
reproduce or a failing test case.
--
Ticket URL: <https://code.djangoproject.com/ticket/35324#comment:2>