I think your problem is not related to the fix below. -- Tatsuo Ishii SRA OSS, Inc. Japan
> Yes, I did have the same problem with 2.2.2. There is a change note that I > thought might fix this problem, so I upgraded to 2.2.3: > > 2009-08-11 22:23 t-ishii > > * pool_connection_pool.c (V2_2_STABLE): Fix new_connection() so > that it does leave garbage in POOL_CONNECTION_POOL->slot[i]. This > caused segfault in child_exit(). Bug report at [pgpool-general-jp: > 586]. > > > > --- On Mon, 8/17/09, Tatsuo Ishii <[email protected]> wrote: > > > From: Tatsuo Ishii <[email protected]> > > Subject: Re: [Pgpool-general] pgpool-II-2.2.3 coredumps repeatedly > > To: [email protected] > > Cc: [email protected], [email protected] > > Date: Monday, August 17, 2009, 4:08 AM > > > > 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
