| From: | murrayc(at)murrayc(dot)com |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #7514: postgres -k no longer works with spaces in the path |
| Date: | 2012-09-01 04:16:57 |
| Message-ID: | E1T7f8j-0007MM-FJ@wrigleys.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 7514
Logged by: Murray Cumming
Email address: murrayc(at)murrayc(dot)com
PostgreSQL version: 9.1.5
Operating system: Fedora Linux 17
Description:
At some point, probably in 9.1.5, the -k option to Postgres ("Unix-domain
socket location" in --help), stopped accepting paths that contain spaces.
For instance,
-k '/tmp/testglom2FPDKW/path with spaces/some_postgres_data'
It now fails with this error:
FATAL: invalid list syntax for "unix_socket_directories"
This is not critical, but it showed up in the regression tests for Glom. And
users are fairly likely to use paths with spaces.
-k apparently accepts a comma-separated list, so there should be no need to
check for spaces.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2012-09-01 06:40:06 | Re: BUG #6239: Looking for a technical contact point for PostgreSQL compatibility issue on Windows8 |
| Previous Message | Craig Ringer | 2012-09-01 00:42:10 | Re: BUG #7513: Cluster install failed |