Opened 12 months ago
Last modified 12 months ago
#35016 closed Cleanup/optimization
Missing documentation for setting libpq options with the PostgreSQL backend — at Initial Version
| Reported by: | Roman Donchenko | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 5.0 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
As far as I can see, when a database uses the django.db.backends.postgresql engine, any options from the OPTIONS key that are not recognized by the engine itself are passed directly to the underlying libpq library. This way you can set options like `sslmode`.
But this doesn't seem to actually be documented anywhere, so it's unclear whether this is actually a supported feature or just an implementation artifact.
If this really is supported, then it should be documented - presumably in PostgreSQL notes.
Note:
See TracTickets
for help on using tickets.