[pgpool-general: 7176] Re: Idle connection in database

Tatsuo Ishii ishii at sraoss.co.jp
Sat Aug 1 22:15:25 JST 2020


> Hi,
> 
> Yes, we can see the pid
> 
> show pool_pools;
> pool_pid |     start_time      | pool_id | backend_id | database |
> username   |     create_time     | majorversion | minorversion |
> pool_counter | pool_backendpid | pool_connected
> 
> 18190    | 2020-08-01 06:14:41 | 0       | 1          | edb      |
> enterprisedb | 2020-08-01 06:19:52 | 3            | 0            | 1
>      | *29321*          | 0
> 18193    | 2020-08-01 06:14:41 | 0       | 1          | edb      |
> enterprisedb | 2020-08-01 06:21:26 | 3            | 0            | 1
>      | *29619          *| 0
> 
> 
> select pid,query,usename,state from pg_stat_activity where
> client_addr='128.199.224.132' group by usename,query,pid;
>  pid  |    query     |   usename    | state
> -------+--------------+--------------+-------
>  *29321 *|  DISCARD ALL | enterprisedb | idle
>  *29619* |  DISCARD ALL | enterprisedb | idle

Assuming you executed "show pool_pools" long after 2020-08-01
06:21:26, that is very strange because connection_life_time should
have been already expired. I wonder if pgpool tried to disconnect the
connection but failed. To check what actually happend, can you check
ps status of pgpool process 18190 and 18193?

Also it would be nice you can examine the socket status of PostgreSQL
backend 29321 and 29619, and pgpool socket status of process 18190 and
18193?

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp


More information about the pgpool-general mailing list