> Hi > > We applied the patch with the same result. After some seconds child > processes go into DEALLOCATE state until pgpool gets completly hang. > > root 592 569 4 23:31 ? 00:00:57 pgpool: sess sess > 127.0.0.1(56552) DEALLOCATE > root 597 569 0 23:31 ? 00:00:03 pgpool: sess sess > 127.0.0.1(37107) DEALLOCATE > root 603 569 4 23:31 ? 00:00:57 pgpool: sess sess > 127.0.0.1(41935) DEALLOCATE > root 615 569 3 23:31 ? 00:00:47 pgpool: sess sess > 127.0.0.1(42742) DEALLOCATE > root 625 569 0 23:31 ? 00:00:09 pgpool: sess sess > 127.0.0.1(34685) DEALLOCATE > root 1173 569 4 23:36 ? 00:00:41 pgpool: sess sess > 127.0.0.1(47999) DEALLOCATE > root 1200 569 1 23:36 ? 00:00:11 pgpool: sess sess > 127.0.0.1(37230) DEALLOCATE > root 1490 569 7 23:38 ? 00:00:57 pgpool: sess sess > 127.0.0.1(60995) DEALLOCATE > root 1512 569 3 23:38 ? 00:00:25 pgpool: sess sess > 127.0.0.1(38378) DEALLOCATE > root 1712 569 4 23:42 ? 00:00:25 pgpool: sess sess > 127.0.0.1(45094) DEALLOCATE > root 1715 569 4 23:42 ? 00:00:23 pgpool: sess sess > 127.0.0.1(34418) DEALLOCATE > > > i attached the complete log for one of these processes. > > > Please any test we can do to help the analsys just let us know.
It seems cause of this is, pgpool sends BEGIN to PostgreSQL and PostgreSQL replies ERROR for unknown reason. I need to know why PostgreSQL emits ERROR. Can you find error messages in the PostgreSQL log? -- Tatsuo Ishii SRA OSS, Inc. Japan _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
