Connect to database using unix socket about queue_classic HOT 4 CLOSED

You could use the default socket location for the postgres unix socket, if you don't specify a host at all.

@ryandotsmith What do you think of changing the way, queue_classic specifies its database settings, so that unix socket locations can also be specified?
Maybe with query strings, like postgres://var/run/postgresql.sock?user=foo&pw=bar&db=mydb
I could send a pull request, if you don't mind adding this to queue_classic.

URI.parse already parses the path and the query string, we would only have to parse the a=b&c=d.. stuff.

The pg driver supports, specifying the socket location as the hostname, but URI.parse does not allow, e.g. postgres://user@/var/run/xy.sock/mydb

Therefore I think, another syntax for unix socket connections would be ok, wouldn't it?

from queue_classic.

@ryandotsmith Would you accept a pull request which makes queue_classic accept unix socket paths in querystring format too, like "postgres://var/run/postgresql.sock?user=foo&pw=bar&db=mydb" ?
(Additionally to the classic URI style..)

from queue_classic.

@ClemensGruber that would be great!

from queue_classic.

After searching mailing lists, I discovered that recent versions of `libpq' should connect to hosts that are actually percent-encoded socket paths. The feature is only documented for PostgreSQL 9.2 and onwards.

In other words, the following kind of database urls should be supported:

postgresql://%2Fvar%2Flib%2Fpostgresql/dbname

Reference: search the "percent" string in http://www.postgresql.org/docs/9.2/interactive/libpq-connect.html

I am now preparing a pull request to fix this issue by adding support for percent-encoded socket paths in DATABASE_URL.

from queue_classic.