This error should not happen. In other word, souds like bug and maybe fixed in the latest version. Please try 2.1. -- Tatsuo Ishii SRA OSS, Inc. Japan
> This morning I was looking at pg_stat_activity table on my master server and > there was a query that was idle in transaction since 2008-12-04 03:35:59 > (several hours). What does this error indicate? > 2008-12-04 03:35:59 ERROR: pid 20905: pool_check_fd: data is not ready > tp->tv_sec 5 tp->tp_usec 0 > 2008-12-04 03:35:59 ERROR: pid 20905: pool_read: pool_check_fd failed > (Unknown error: 0) > 2008-12-04 04:13:25 ERROR: pid 29555: pool_check_fd: data is not ready > tp->tv_sec 5 tp->tp_usec 0 > 2008-12-04 04:13:25 ERROR: pid 29555: pool_read: pool_check_fd failed > (Unknown error: 0) > 2008-12-04 04:13:25 ERROR: pid 29555: SimpleForwardToFrontend: malloc failed > 2008-12-04 04:13:25 LOG: pid 29555: do_child: exits with status 1 due to > error > 2008-12-04 04:26:28 ERROR: pid 22682: pool_check_fd: data is not ready > tp->tv_sec 5 tp->tp_usec 0 > 2008-12-04 04:26:28 ERROR: pid 22682: pool_read: pool_check_fd failed > (Unknown error: 0) > 2008-12-04 04:26:28 ERROR: pid 22682: SimpleForwardToFrontend: malloc failed > 2008-12-04 04:26:28 LOG: pid 22682: do_child: exits with status 1 due to > error > > Killing the query on the master caused pgpool to no longer accept > connections until it was restarted. > > pgpool-II version 2.0.1 > slony 1.2.11 used for replication > (PostgreSQL) 8.2.3 > > thanks in advance, > > bruce _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
