You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you use the native API and specify a UNIX socket in the connectionString URL, then the actual string passed to the native API incorrectly includes the port, user, and password parameters. This will force postgres to try to connect using a TCP socket, instead of the given UNIX socket.
For example, if I specify postgres:///foo for my connectionString, then I would expect this string to be passed to the connect function without alteration. Instead, the connection string ends up as:
If you use the native API and specify a UNIX socket in the connectionString URL, then the actual string passed to the native API incorrectly includes the port, user, and password parameters. This will force postgres to try to connect using a TCP socket, instead of the given UNIX socket.
This is most likely due to an issue in the ConnectionParameters#getLibpqConnectionString function.
For example, if I specify postgres:///foo for my connectionString, then I would expect this string to be passed to the connect function without alteration. Instead, the connection string ends up as:
user='josh' port='5432' dbname='foo' host=localhost hostaddr=127.0.0.1
The text was updated successfully, but these errors were encountered: