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 password to health_check_user. Is your health_check_user trust authentication? -- Toshihiro Kitagawa SRA OSS, Inc. Japan On Sun, 4 Sep 2011 19:00:14 -0700 Lonni J Friedman <netll...@gmail.com> wrote: > On Sun, Sep 4, 2011 at 5:36 PM, Rosser Schwarz <rosser.schw...@gmail.com> > wrote: > > "Unexpected EOF" doesn't mean a postgres backend is failing; it > > typically means that a client has disconnected from its backend > > without closing out the session. (E.g., connect via psql, then kill > > the psql process -- not the backend! -- and you'll see an "Unexpected > > EOF".) > > > > As for why you're only seeing them since starting to use pgpool, I > > couldn't say. I'm seeing them, too, but was before we started working > > with the pooler, too, and haven't noticed (but also haven't > > specifically looked for) a change in their frequency. > > Weird. I guess I can ignore it for now, as I haven't noticed any > negative side effects. It would be nice if there was an effective > means of debugging it though (other than turning on SQL logging, which > is going to fill up my disks in a matter of hours). > _______________________________________________ > Pgpool-general mailing list > Pgpool-general@pgfoundry.org > http://pgfoundry.org/mailman/listinfo/pgpool-general _______________________________________________ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general