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
It seems that if I run my tests with a default configuration and have the environment variable PGUSER unset, everything goes well.
However, if I have PGUSER set to postgres, for instance, I get a ConnectionTimedOut error.
By inspecting with netstat and manually connecting with psql while I wait for the timeout, it seems that the postgres user hasn't been created but is used by tmp-postgres when it tries to connect. Instead, my current user (mzabani in my case) is able to connect to the postgres DB but is not used by tmp-postgres when it tries to connect.
I'm not sure if this is actually a bug since I just started using tmp-postgres, so sorry if this is noise, and thanks for the library!
The text was updated successfully, but these errors were encountered:
The code that calls initdb uses the PGUSER environment for role creation but I don't think I use it for the connections parameters. I need process that is consistent so I should probably support the PGUSER in both cases.
It seems that if I run my tests with a default configuration and have the environment variable
PGUSER
unset, everything goes well.However, if I have
PGUSER
set to postgres, for instance, I get aConnectionTimedOut
error.By inspecting with
netstat
and manually connecting withpsql
while I wait for the timeout, it seems that thepostgres
user hasn't been created but is used by tmp-postgres when it tries to connect. Instead, my current user (mzabani
in my case) is able to connect to the postgres DB but is not used by tmp-postgres when it tries to connect.I'm not sure if this is actually a bug since I just started using tmp-postgres, so sorry if this is noise, and thanks for the library!
The text was updated successfully, but these errors were encountered: