#36960: Django never uses psycopg 3's optimised timestamptzloader
-------------------------------------+-------------------------------------
Reporter: Aarni Koskela | Owner: (none)
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 6.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: postgresql | Triage Stage:
| Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* resolution: wontfix =>
* stage: Unreviewed => Someday/Maybe
* status: closed => new
Comment:
Great plan. I'll signal that by moving this to Someday/Maybe to represent
we're waiting on upstream input.
--
Ticket URL: <https://code.djangoproject.com/ticket/36960#comment:3>
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/0107019cafa0b2dd-61348eff-a31a-4e31-a200-3872ef94b938-000000%40eu-central-1.amazonses.com.
