My guess is DEALLOCATE is being issued at end of session between pgpool and PostgreSQL. For some reason PostgreSQL returns weired packet kind 0x73 on node 0 and 0x84 on node 1.
Anyway, I need more information. Do you find some errors in PostgreSQL log? What kind of difference are there in your databases? -- Tatsuo Ishii SRA OSS, Inc. Japan > Hi, > > I'm testing pgpool 2.2.4 with some problems.... i hope someone can > help me to figure out what the problem is. > > > I have two backends that unfortunately have diferences, that's the > initial scenario when i started pgpool, everything goes well for some > seconds but after a while a lot of error come out: > > (filtered output) > 2009-09-11 02:19:03 ERROR: pid 28468: pool_flush_it: write failed > (Broken pipe) offset: 0 wlen: 12 > 2009-09-11 02:19:03 ERROR: pid 27857: pool_flush_it: write failed > (Broken pipe) offset: 0 wlen: 12 > 2009-09-11 02:19:03 ERROR: pid 27857: pool_read_kind: kind does not > match between master(73) slot[1] (84) > 2009-09-11 02:19:03 ERROR: pid 28235: pool_read_kind: kind does not > match between master(84) slot[1] (73) > 2009-09-11 02:19:03 ERROR: pid 28414: pool_flush_it: write failed > (Broken pipe) offset: 0 wlen: 12 > 2009-09-11 02:19:03 ERROR: pid 27866: pool_flush_it: write failed > (Broken pipe) offset: 0 wlen: 12 > 2009-09-11 02:19:03 ERROR: pid 28414: pool_read_kind: kind does not > match between master(73) slot[1] (84) > 2009-09-11 02:19:03 ERROR: pid 28310: pool_flush_it: write failed > (Broken pipe) offset: 0 wlen: 12 > 2009-09-11 02:19:03 ERROR: pid 28469: pool_read_kind: kind does not > match between master(73) slot[1] (84) > 2009-09-11 02:19:03 ERROR: pid 28419: pool_flush_it: write failed > (Broken pipe) offset: 0 wlen: 5 > 2009-09-11 02:19:03 ERROR: pid 28419: pool_flush_it: write failed > (Broken pipe) offset: 0 wlen: 149 > 2009-09-11 02:19:03 ERROR: pid 27866: pool_read_kind: kind does not > match between master(84) slot[1] (73) > 2009-09-11 02:19:03 ERROR: pid 28310: pool_read_kind: kind does not > match between master(84) slot[1] (73) > 2009-09-11 02:19:03 ERROR: pid 28221: pool_flush_it: write failed > (Broken pipe) offset: 0 wlen: 5 > > pgpool processes go from: > > root 28166 27814 0 02:13 ? 00:00:00 pgpool: wait for > connection request > root 28167 27814 0 02:13 ? 00:00:00 pgpool: wait for > connection request > root 28169 27814 6 02:13 ? 00:00:10 pgpool: sess sess > 127.0.0.1(43911) DEALLOCATE > root 28170 27814 0 02:13 ? 00:00:00 pgpool: wait for > connection request > root 28174 27814 0 02:13 ? 00:00:00 pgpool: sess sess > 127.0.0.1(35292) idle > root 28178 27814 1 02:13 ? 00:00:02 pgpool: sess sess > 127.0.0.1(44647) DEALLOCATE > root 28179 27814 1 02:13 ? 00:00:02 pgpool: sess sess > 127.0.0.1(47125) DEALLOCATE > root 28181 27814 0 02:13 ? 00:00:00 pgpool: wait for > connection request > root 28182 27814 0 02:13 ? 00:00:00 pgpool: sess sess > 127.0.0.1(52477) idle > root 28187 27814 0 02:13 ? 00:00:00 pgpool: wait for > connection request > root 28193 27814 0 02:14 ? 00:00:00 pgpool: wait for > connection request > root 28194 27814 0 02:14 ? 00:00:00 pgpool: wait for > connection request > root 28195 27814 0 02:14 ? 00:00:00 pgpool: wait for > connection request > > > to: > > root 27853 27814 0 02:11 ? 00:00:01 pgpool: sess sess > 127.0.0.1(58341) DEALLOCATE > root 27887 27814 7 02:11 ? 00:00:21 pgpool: sess sess > 127.0.0.1(49142) DEALLOCATE > root 27897 27814 4 02:11 ? 00:00:14 pgpool: sess sess > 127.0.0.1(58998) DEALLOCATE > root 27922 27814 5 02:11 ? 00:00:16 pgpool: sess sess > 127.0.0.1(49541) DEALLOCATE > root 27923 27814 11 02:11 ? 00:00:34 pgpool: sess sess > 127.0.0.1(36883) DEALLOCATE > root 27933 27814 7 02:11 ? 00:00:21 pgpool: sess sess > 127.0.0.1(42722) DEALLOCATE > root 27937 27814 7 02:11 ? 00:00:22 pgpool: sess sess > 127.0.0.1(52656) DEALLOCATE > root 27939 27814 3 02:11 ? 00:00:10 pgpool: sess sess > 127.0.0.1(47648) DEALLOCATE > root 27947 27814 11 02:11 ? 00:00:35 pgpool: sess sess > 127.0.0.1(44597) DEALLOCATE > root 27952 27814 5 02:11 ? 00:00:16 pgpool: sess sess > 127.0.0.1(57546) DEALLOCATE > root 27954 27814 11 02:11 ? 00:00:34 pgpool: sess sess > 127.0.0.1(50946) DEALLOCATE > root 28155 27814 2 02:12 ? 00:00:04 pgpool: sess sess > 127.0.0.1(47095) DEALLOCATE > root 28159 27814 0 02:13 ? 00:00:00 pgpool: sess sess > 127.0.0.1(52691) DEALLOCATE > root 28163 27814 6 02:13 ? 00:00:10 pgpool: sess sess > 127.0.0.1(56219) DEALLOCATE > root 28169 27814 6 02:13 ? 00:00:11 pgpool: sess sess > 127.0.0.1(43911) DEALLOCATE > root 28178 27814 1 02:13 ? 00:00:02 pgpool: sess sess > 127.0.0.1(44647) DEALLOCATE > > > And then everything stop working.... > > > Is this a normal behaviour when backends are diferents? What can be > the reason for children going to DEALLOCATE state? > > > Thanks in Advance > Agustín Almonte F. > > > > > > _______________________________________________ > 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
