Closed xicesky closed 7 years ago
@xicesky Did you finally find any workaround for this?
Yes, by using TCP instead, and setting up password authentication for the user that imposm uses to connect to the Database. Since this worked for me, i didn't bother trying to patch the code.
OK, this is what I'm doing locally, but I don't like having password in my servers ;) I'll see for a better option later. Thanks for your answer :)
A workaround is
PGHOST=/path/to/socket/directory/ imposm3 ... -connection="postgis:///dbname" ...
-connection='postgis: dbname=osm host=/path/to/socket'
is now supported with 29d1882
A workaround is
PGHOST=/path/to/socket/directory/ imposm3 ... -connection="postgis:///dbname" ...
THANK YOU. That helped me alot
With imposm2 i could use postgis:///mapnik to use the unix socket. But:
gives me:
It does not seem possible to specify a socket path directly using the URL syntax, because lib/pq splits the host name after the first slash. (e.g. you cannot write "postgis:///var/run/postgresql/mapnik")
So i tried the following:
but still:
I am not a go expert, but is there a way to tell imposm (or lib/pq) to not use password auth?