#36960: Django never uses psycopg 3's optimised timestamptzloader
-------------------------------------+-------------------------------------
Reporter: Aarni Koskela | Owner: Aarni
Type: | Koskela
Cleanup/optimization | Status: closed
Component: Database layer | Version: 6.0
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: postgresql | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls <jacobtylerwalls@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"994fa7780d73f6d618dc3a03339e96b5353b4e71" 994fa77]:
{{{#!CommitTicketReference repository=""
revision="994fa7780d73f6d618dc3a03339e96b5353b4e71"
Fixed #36960 -- Enabled the use of psycopg 3's optimized timestamp loader.
Based on Daniele Varrazzo's comment in
https://github.com/psycopg/psycopg/issues/1273#issuecomment-3986829769
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36960#comment:8>
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/0107019d0cf22bac-6e20fd0e-184d-4ca2-8626-caf2e1ed948d-000000%40eu-central-1.amazonses.com.
