[Pgpool-general] Why pgpool II always refuses connections?

Zhidong She zhidong.she at gmail.com
Tue Dec 21 09:23:07 UTC 2010


Hi all,

We are testing pgpool II by pgbench, when we use below command to do the
test, the pgpool runs ok.
/opt/PostgreSQL/8.4/bin/pgbench -t 2000 -c 20 -h 172.17.3.10 -p 9999 -U
postgres pgbench

But if we add "-C" option, which means to establish new connection for every
transaction, the pgpool II will always refuse the connections after about
28230 successful connection.
/opt/PostgreSQL/8.4/bin/pgbench -t 2000 -C -c 20 -h 172.17.3.10 -p 9999 -U
postgres pgbench

I tried many times, and the number of transactions actually processed is
always at 28232 or so.

Please see below the detail infomation, any pgpool arguments need to be
adjusted to avoid this issue?

Thanks very much for your help!!!

=======================================================================================
[root at ucs09 shell]# /opt/PostgreSQL/8.4/bin/pgbench -C -t 2000 -c 20 -h
172.17.3.10 -p 9999 -U postgres pgbench
starting vacuum...end.
Connection to database "pgbench" failed:
could not connect to server: Cannot assign requested address
        Is the server running on host "172.17.3.10" and accepting
        TCP/IP connections on port 9999?
Client 12 aborted in establishing connection.
Connection to database "pgbench" failed:
could not connect to server: Cannot assign requested address
        Is the server running on host "172.17.3.10" and accepting
        TCP/IP connections on port 9999?
Client 13 aborted in establishing connection.
Connection to database "pgbench" failed:
could not connect to server: Cannot assign requested address
        Is the server running on host "172.17.3.10" and accepting
        TCP/IP connections on port 9999?
Client 3 aborted in establishing connection.
Connection to database "pgbench" failed:
could not connect to server: Cannot assign requested address
        Is the server running on host "172.17.3.10" and accepting
        TCP/IP connections on port 9999?
Client 0 aborted in establishing connection.
Connection to database "pgbench" failed:
could not connect to server: Cannot assign requested address
        Is the server running on host "172.17.3.10" and accepting
        TCP/IP connections on port 9999?
Client 16 aborted in establishing connection.
Connection to database "pgbench" failed:
could not connect to server: Cannot assign requested address
        Is the server running on host "172.17.3.10" and accepting
        TCP/IP connections on port 9999?
Client 8 aborted in establishing connection.
Connection to database "pgbench" failed:
could not connect to server: Cannot assign requested address
        Is the server running on host "172.17.3.10" and accepting
        TCP/IP connections on port 9999?
Client 4 aborted in establishing connection.
Connection to database "pgbench" failed:
could not connect to server: Cannot assign requested address
        Is the server running on host "172.17.3.10" and accepting
        TCP/IP connections on port 9999?
Client 5 aborted in establishing connection.
Connection to database "pgbench" failed:
could not connect to server: Cannot assign requested address
        Is the server running on host "172.17.3.10" and accepting
        TCP/IP connections on port 9999?
Client 1 aborted in establishing connection.
Connection to database "pgbench" failed:
could not connect to server: Cannot assign requested address
        Is the server running on host "172.17.3.10" and accepting
        TCP/IP connections on port 9999?
Client 9 aborted in establishing connection.
Connection to database "pgbench" failed:
could not connect to server: Cannot assign requested address
        Is the server running on host "172.17.3.10" and accepting
        TCP/IP connections on port 9999?
Client 10 aborted in establishing connection.
Connection to database "pgbench" failed:
could not connect to server: Cannot assign requested address
        Is the server running on host "172.17.3.10" and accepting
        TCP/IP connections on port 9999?
Client 2 aborted in establishing connection.
Connection to database "pgbench" failed:
could not connect to server: Cannot assign requested address
        Is the server running on host "172.17.3.10" and accepting
        TCP/IP connections on port 9999?
Client 6 aborted in establishing connection.
Connection to database "pgbench" failed:
could not connect to server: Cannot assign requested address
        Is the server running on host "172.17.3.10" and accepting
        TCP/IP connections on port 9999?
Client 11 aborted in establishing connection.
Connection to database "pgbench" failed:
could not connect to server: Cannot assign requested address
        Is the server running on host "172.17.3.10" and accepting
        TCP/IP connections on port 9999?
Client 15 aborted in establishing connection.
Connection to database "pgbench" failed:
could not connect to server: Cannot assign requested address
        Is the server running on host "172.17.3.10" and accepting
        TCP/IP connections on port 9999?
Client 14 aborted in establishing connection.
Connection to database "pgbench" failed:
could not connect to server: Cannot assign requested address
        Is the server running on host "172.17.3.10" and accepting
        TCP/IP connections on port 9999?
Client 7 aborted in establishing connection.
Connection to database "pgbench" failed:
could not connect to server: Cannot assign requested address
        Is the server running on host "172.17.3.10" and accepting
        TCP/IP connections on port 9999?
Client 17 aborted in establishing connection.
Connection to database "pgbench" failed:
could not connect to server: Cannot assign requested address
        Is the server running on host "172.17.3.10" and accepting
        TCP/IP connections on port 9999?
Client 18 aborted in establishing connection.
Connection to database "pgbench" failed:
could not connect to server: Cannot assign requested address
        Is the server running on host "172.17.3.10" and accepting
        TCP/IP connections on port 9999?
Client 19 aborted in establishing connection.
transaction type: TPC-B (sort of)
scaling factor: 20
query mode: simple
number of clients: 20
number of transactions per client: 2000
number of transactions actually processed: 28232/40000
tps = 841.807364 (including connections establishing)
tps = 2069.595197 (excluding connections establishing)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pgfoundry.org/pipermail/pgpool-general/attachments/20101221/1dc18910/attachment.html>


More information about the Pgpool-general mailing list