proxy did not work with PG10

[jmccormick2001]

trafficstars

in testing, the proxy appears to not work with PG10.0.

[k1ng440]

does it support PG11?

[emmetog]

Just a guess here as I've run into an issue when trying to use postgresql 10, but is below the same problem you had?

When starting up everything looks good:

INFO[2021-01-21T15:11:09Z] Authenticating with MD5 password.            
INFO[2021-01-21T15:11:09Z] Successfully connected to 'db01' at '10.0.0.6:5432' 
INFO[2021-01-21T15:11:09Z] Connecting to node 'db02' at 10.0.0.8:5432... 
INFO[2021-01-21T15:11:09Z] Authenticating with MD5 password.            
INFO[2021-01-21T15:11:09Z] Successfully connected to 'db02' at '10.0.0.8:5432' 
INFO[2021-01-21T15:11:09Z] Connecting to node 'db02' at 10.0.0.8:5432... 
INFO[2021-01-21T15:11:09Z] Authenticating with MD5 password.            
INFO[2021-01-21T15:11:09Z] Successfully connected to 'db02' at '10.0.0.8:5432' 

When a client tries to connect, things go sideways:

INFO[2021-01-21T15:11:14Z] Client: 10.0.0.8:53332 - authenticating      
DEBU[2021-01-21T15:11:14Z] client auth: connecting to 'master' node     
ERRO[2021-01-21T15:11:14Z] An error occurred connecting to the master node 
ERRO[2021-01-21T15:11:14Z] Error dial tcp: missing address              
ERRO[2021-01-21T15:11:14Z] Client: 10.0.0.8:53332 - authentication failed 
ERRO[2021-01-21T15:11:14Z] Error: dial tcp: missing address             

EDIT: This is with the latest released binary of crunchy-proxy v1.0.0beta, so may not be latest master.

[emmetog]

Strangely the connection via psql seem to work fine with crunchy-proxy-0.0.1-alpha, after having converted the yaml config file to json using the template here as a base and running it like this:

$ crunchy-proxy-0.0.1-alpha -config /etc/cruncy-proxy/config.json -v 5