#21296 closed Cleanup/optimization (fixed)
settings: adding a the unix socket dir path in DATABASES HOST works for postgres too
| Reported by: | rm_ | Owned by: | rm_ |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Normal | Keywords: | postgres settings host |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The host documentation [1] doesn't mention that passing a unix socket dir (unix_socket_directory in postgresql.conf) as value of HOST will have postgresql use that instead of default /var/run/postgresql/.s.PGSQL.5432 . Since there is an explicit example for MySQL i thought it wasn't supported (i've tried it though :). Tested with django 1.5.4 / postgresql_psycopg2
There are also a couple of stack overflow questions related to this:
http://stackoverflow.com/questions/12317562/trying-to-set-django-and-postgresql-on-heroku
http://stackoverflow.com/questions/10829464/postgresql-and-django-unix-domain-socket
[1] https://docs.djangoproject.com/en/dev/ref/settings/#host
Change History (7)
comment:1 by , 12 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|---|
| Type: | Uncategorized → Cleanup/optimization |
| Version: | 1.5 → master |
comment:2 by , 12 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
| Triage Stage: | Accepted → Unreviewed |
comment:3 by , 12 years ago
| Has patch: | set |
|---|
comment:4 by , 12 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:5 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
Opened a pull request https://github.com/django/django/pull/1786