#37075: `OPTIONS["pool"]["check"]` cannot be set: the PostgreSQL backend always
passes `check=` to `psycopg_pool.ConnectionPool`, then unpacks
`**pool_options` on top, raising `TypeError`.
-------------------------------------+-------------------------------------
Reporter: Raoni Timo de | Owner: Raoni
Castro Cambiaghi | Timo de Castro Cambiaghi
Type: | Status: assigned
Cleanup/optimization |
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: postgresql psycopg | Triage Stage: Accepted
pool |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* owner: (none) => Raoni Timo de Castro Cambiaghi
* stage: Unreviewed => Accepted
* status: new => assigned
* type: Bug => Cleanup/optimization
Comment:
Makes sense. Thanks for offering a PR. (We probably want to unpack the
provided kwargs into a copy before mutating.)
I guess we have the same situation with `configure`, but we don't have to
address that now.
--
Ticket URL: <https://code.djangoproject.com/ticket/37075#comment:1>
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/0107019ddaa18507-9e6e85f0-3d70-483f-915b-4e8c04ad8dc4-000000%40eu-central-1.amazonses.com.
