Opened 3 years ago
Closed 3 years ago
#35324 closed Bug (invalid)
Postgres Extensions Not Available
| Reported by: | Fred Lamming | Owned by: | Fred Lamming |
|---|---|---|---|
| Component: | contrib.postgres | Version: | 5.0 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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.
Change History (2)
comment:1 by , 3 years ago
| Owner: | set to |
|---|---|
| Status: | new → assigned |
comment:2 by , 3 years ago
| Has patch: | unset |
|---|---|
| Resolution: | → invalid |
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
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 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.