allow connection to unix domain sockets via 'pq://' locator strings

[avbidder]

I'm not sure if this is a wishlist bug or a documentation bug.

I'd like to connect to my database via unix socket. How should my locator string look like? (I'd really like to use a locator string, since I then can just read that string from the configuration)

Ideally: 'pq:///' would just connect to the default database by the default unix socket that is used on my OS. 'pq:///dbname' would be the obvious way to specify a database. Not sure about a syntax when my unix socket is not at the default location.

[jwp]

There is support for unix sockets in the PQ locator strings. However, I left it undocumented [and perhaps untested] as it's a bit funky: =)

pq://[unix:path:to:file]/dbname

Yes, colons are the path separator. It was done this way because the existing locator parser leaned heavily on '/' being .find()'able.

Also, I think part of the reason for the cop-out is that I expected people to just use the 'unix' keyword parameter in these situations.

[avbidder]

Hmm. Perhaps pq:///database?socket=path/to/socket

(Since the old syntax was undocumented, should be no problem to change...)

Having the full connction info in one string makes configuration files much easier than having to fiddle with different types of connections in the config file (or only being able to support tcp in the config file.)

[jwp]

Already available.