> Simone Tregnago wrote: > > Hi all, > > I've started some tests in order to try the switch from > > pgpool 2.1 to 2.2. > > Unfortunately, when the client executes an update, pgpool crashes with > > a segfault. > > this is the second time that I got in trouble with pgpool but there > isn't anyone that takes care to reply to me: maybe there's something bad > in the way that I write my emails? Or my troubles are so stupid? Don't > know, I think that a segfault is a kind of bug that needs a bit of > attention in a release. Don't know how to do more tests, don't know > how to report more details, if needed. > I had let alone, as the last time. > My last bug report had forgiven in the same way, without a single reply. > Please, let me know if using pgpool means: debug, modify and recompile > every time you'll find a bug that doesn't hurt the team. > Regards
I have tried to reproduce your problem without sunccess, so I was watching someone coming out with similar problem(it seems it's just an ordinarly update...). Can you provide self contained test case or a stack trace with -g (and without -O2) comipled binary? -- Tatsuo Ishii SRA OSS, Inc. Japan _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
