Skip to content
This repository has been archived by the owner on Apr 2, 2024. It is now read-only.

Fail to use unix sockets (URI parsing issues) #1783

Open
kworr opened this issue Dec 5, 2022 · 0 comments
Open

Fail to use unix sockets (URI parsing issues) #1783

kworr opened this issue Dec 5, 2022 · 0 comments
Assignees
Labels
Bug Something isn't working

Comments

@kworr
Copy link

kworr commented Dec 5, 2022

Describe the bug
When setting host to point to UNIX socket path it picked up correctly and URI is constructed correctly. However when attempting to connect:

promscale[27837]: level=error ts=2022-12-05T06:30:47.822Z caller=runner.go:127 msg="aborting startup due to error" err="cannot parse postgresql://postgres:@%2Ftmp%2F.s.PGSQL.5432:5432/timescale?application_name=promscale%400.16.0&connect_timeout=60&sslmode=require: failed to parse as URL (parse "postgresql://postgres:@%2Ftmp%2F.s.PGSQL.5432:5432/timescale?application_name=promscale%400.16.0&connect_timeout=60&sslmode=require": invalid URL escape "%2F")"

To Reproduce
Set -db.host to /tmp/.s.PGSQL.5432 (and -db.name).

Expected behavior
Escape patterns accepted. They are used to hide "/" in database name part.

Version

  • Distribution/OS: FreeBSD STABLE-13.1
  • Promscale: 0.16.0

--
Might be just required library is not enabling proper UNIX sockets support.

@jgpruitt jgpruitt self-assigned this Dec 8, 2022
@ramonguiu ramonguiu added the Bug Something isn't working label Dec 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants