Hi Chaps, We currently use pgpool-II purely as a pool/proxy, and one thing I did notice when we first moved to 2.2.2 was that I'd get a segfault in pgpool if I took down the postgres server it was connected to. I'm pretty sure it didn't happen back in 2.1 (my memory of of going from 2.2, 2.2.1 etc is a it fuzzy now), but since it was otherwise pretty stable and I was busy I never mentioned it.
We also have child_life_time set to 300 so will give 2.2.3 a whirl too and see what happens. glyn ----- Original Message ---- > From: Tatsuo Ishii <[email protected]> > To: [email protected] > Cc: [email protected] > Sent: Monday, 17 August, 2009 9:08:10 > Subject: Re: [Pgpool-general] pgpool-II-2.2.3 coredumps repeatedly > > > > The problem goes away when child_life_time is set to zero. Also, it > > > always > happens when my_proc_id = 8, never some other number. > > > > Never had it set to any other value but zero. That must be the reason > > why I've never had this error :-S > > I've set it to 300 for years but never had the same problem Bob has. > > I wonder if he had the problem when he uses 2.2.2. > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > _______________________________________________ > Pgpool-general mailing list > [email protected] > http://pgfoundry.org/mailman/listinfo/pgpool-general _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
