On Mon, Sep 12, 2011 at 3:34 AM, Toshihiro Kitagawa
kitag...@sraoss.co.jp wrote:
Hi,
However, I'm see tons (dozens every minute) of the
following in my postgresql server logs:
LOG: unexpected EOF on client connection
I found recently that it occurs if you specify the role that needs a
Thanks for your quick reply! I figured this out on my own about 2
minutes ago. All good now.
On Mon, Sep 12, 2011 at 10:24 AM, daniel.cre...@l-3com.com wrote:
You have to use pcp_attach_node command to re-attach that node. Pgpool
doesn't know if a database that went down is in good shape
You have to use pcp_attach_node command to re-attach that node. Pgpool
doesn't know if a database that went down is in good shape even if it is
back online. So, after you perform the synching (it seems like you did),
call the pcp_attach_node to bring it back to pgpool's pool of databases.
-Daniel
Yes, all connections defined in pool_hba.conf are trust auth.
However, I also have
health_check_period = 0
in pgpool.conf, so I'd assume that no health checks are being performed?
Have you changed child_life_time or something from defaults? I would
like to take a look at your pgpool.conf.
--
On Mon, Sep 12, 2011 at 5:14 PM, Tatsuo Ishii is...@sraoss.co.jp wrote:
On Mon, Sep 12, 2011 at 4:16 PM, Tatsuo Ishii is...@sraoss.co.jp wrote:
Yes, all connections defined in pool_hba.conf are trust auth.
However, I also have
health_check_period = 0
in pgpool.conf, so I'd assume that no
On Mon, Sep 12, 2011 at 6:39 PM, Tatsuo Ishii is...@sraoss.co.jp wrote:
I couldn't find anything possibly related to your problem at a first
grance(in theory client_idle_limit and authentication_timeout are not
related but you might want to change them to see anything could be
changed).
OK,
