Looks like a bug. Can you please open up an issue? My guess is that the root cause is something related to permission. Maybe the user does not exist or does not have access to access that database or socket connections are forbidden. There is a postgres configuration follow to set those.
