[Pgpool-general] psql : server closed the connection unexpectedly

tried using 2.3.22 or 2.3.3 LOG: 2010-05-11 06:52:12 DEBUG: pid 4348: I am 4348 2010-05-11 06:52:12 DEBUG: pid 4349: I am 4349 2010-05-11 06:52:12 DEBUG: pid 4350: I am 4350 2010-05-11 06:52:12 DEBUG: pid 4351: I am 4351 2010-05-11 06:52:12 DEBUG: pid 4352: I am 4352 2010-05-11 06:52:12 DEBUG:

Re: [Pgpool-general] psql : server closed the connection unexpectedly

sorry, looking at postgres logs I saw that pgpool couldn't connect to 'localhost' because of pg_hba issue tried using 2.3.22 or 2.3.3 LOG: 2010-05-11 06:52:12 DEBUG: pid 4348: I am 4348 2010-05-11 06:52:12 DEBUG: pid 4349: I am 4349 2010-05-11 06:52:12 DEBUG: pid 4350: I am 4350

Re: [Pgpool-general] psql: server closed the connection unexpectedly

I'm still having this issue, pgpool-II cannot connect to the backends after upgrading to version 2.3. The other pgpool (which connects to the same backend servers and runs the same pgpool version with identical configuration) does connect. If I become user postgres, I can 'psql' into the

Re: [Pgpool-general] psql: server closed the connection unexpectedly

Tatsuo Ishii wrote: I'm still having this issue, pgpool-II cannot connect to the backends after upgrading to version 2.3. The other pgpool (which connects to the same backend servers and runs the same pgpool version with identical configuration) does connect. If I become user postgres, I can

Re: [Pgpool-general] psql: server closed the connection unexpectedly

It is absolutely better to run pgpool as postgres, no doubt about it. :) I've taken a look at the pg_hba.conf files of the servers and they generally trust anything that comes from the pgpool ip. I ran pgpool as root again to rule out that running it as postgres is not causing the problem.