#36960: Django never uses psycopg 3's optimised timestamptzloader
-------------------------------------+-------------------------------------
Reporter: Aarni Koskela | Owner: (none)
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 6.0
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: postgresql | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Aarni Koskela):
> a public API from psycopg for retrieving the c-accelerated internals
(unlikely...)
I'm not sure that's totally implausible; the author/maintainer of
psycopg3, @dvarrazzo-on-GitHub, chimed in on the original issue porting
his psycopg3 backend to Django in
[https://github.com/django/django/pull/15687#issuecomment-1348923713], and
is responsive on the psycopg repo (I've been looking at some perf fixes on
that side of the fence.)
I could make a PR there to propose making `get_optimised` a public API,
and link this thread.
--
Ticket URL: <https://code.djangoproject.com/ticket/36960#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019caf98c7b3-fd6c25f1-4aa0-46c8-a476-f9f25c8359ee-000000%40eu-central-1.amazonses.com.
