PCP_PROC_INFO(1)
π PCP_PROC_INFO(1) β like, the pgpool-II 4.7.2 manual, but bestie-fied π
okay so hi, welcome to section 1 of the pgpool-II 4.7.2 docs, this is pcp_proc_info, and she is literally the girl who spills the tea on a Pgpool-II child process. no cap. π«β¨
β¨ NAME β¨
pcp_proc_info β shows you all the info on the Pgpool-II child process ID you hand her. it's giving receipts. π§Ύ
πΈ SYNOPSIS πΈ
pcp_proc_info [options...] [pgpool_child_processid]
π¦ DESCRIPTION π¦
pcp_proc_info displays the information on the given Pgpool-II child process ID.
that's it, that's the whole vibe. you give her a child process ID, she tells you everything about it. main character behavior honestly. π
π OPTIONS π
-a,--allβ display all child processes and their available connection slots. the full group chat, everyone's here. π¬-P PID,--process-id=PIDβ PID of the Pgpool-II child process. like, specifically this one.
π Other options
π«Ά heads up bestie: if neither-anor-Pis not specified, process information of all connected Pgpool-II child process will be printed. In this case if there's no connected Pgpool-II child process, nothing but"No process information available"message will be printed. so like... you get something. sometimes that something is just a little sad sentence. π
π₯ EXAMPLE π₯
here's an example output, look at her go:
$ pcp_proc_info -p 11001
test t-ishii 2025-06-24 10:53:35 0 3 0 2025-06-24 10:55:58 2025-06-24 10:55:59 0 1 1336703 1 1336537 0 Idle 0 192.168.10.11 39216
test t-ishii 2025-06-24 10:53:35 0 3 0 2025-06-24 10:55:58 2025-06-24 10:55:59 0 1 1336704 1 1336537 1 Idle 1 192.168.10.11 39216
test t-ishii 2025-06-24 10:53:35 (4:03 before process restarting) 1 3 0 2025-06-24 10:53:42 2025-06-24 10:53:42 0 2025-06-24 10:55:37 1 1336573 0 1336544 0 Wait for connection 0 192.168.10.11 39162
test t-ishii 2025-06-24 10:53:35 (4:03 before process restarting) 1 3 0 2025-06-24 10:53:42 2025-06-24 10:53:42 0 2025-06-24 10:55:37 1 1336574 0 1336544 1 Wait for connection 0 192.168.10.11 39162
the result is in the following order, and yes you need all 20, she does not skip steps:
- connected database name
- connected user name
- process start-up timestamp (If
child_life_timeis set not0, the time before process restarting is displayed.) - process-reuse counter for
child_max_connections - protocol major version
- protocol minor version
- connection created timestamp
- last client connected timestamp
- client idle duration (sec) (If
client_idle_limitis set not0, the time before client disconnected is displayed.) - last client disconnected timestamp
- connection-reuse counter
- PostgreSQL backend process id
1if frontend connected0if not- pgpool child process id
- PostgreSQL backend id
- process status
1if backend is load balance node and frontend connected,0otherwise- client's host name
- client's port number (not shown if Unix domain socket or localhost)
- SQL statement last executed
ngl that's a lot of columns. slay. π
If -a or --all option is not specified and there is no connection to the backends, nothing will be displayed. If there are multiple connections, one connection's information will be displayed on each line multiple times. Timestamps are displayed in EPOCH format.
the --verbose option can help understand the output. for example:
$ pcp_proc_info -p 11001 --verbose
Database : test
Username : t-ishii
Start time : 2025-06-24 10:53:35
Client connection count : 0
Major : 3
Minor : 0
Backend connection time : 2025-06-24 10:55:58
Client connection time : 2025-06-24 10:55:59
Client idle duration : 0
Client disconnection time :
Pool Counter : 1
Backend PID : 1336703
Connected : 1
PID : 1336537
Backend ID : 0
Status : Idle
Load balance node : 0
client_host : 192.168.10.11
client_port : 39216
statement :
Database : test
Username : t-ishii
Start time : 2025-06-24 10:53:35
Client connection count : 0
Major : 3
Minor : 0
Backend connection time : 2025-06-24 10:55:58
Client connection time : 2025-06-24 10:55:59
Client idle duration : 0
Client disconnection time :
Pool Counter : 1
Backend PID : 1336704
Connected : 1
PID : 1336537
Backend ID : 1
Status : Idle
Load balance node : 1
client_host : 192.168.10.11
client_port : 39216
statement : select 1;
Database : test
Username : t-ishii
Start time : 2025-06-24 10:53:35 (4:33 before process restarting)
Client connection count : 1
Major : 3
Minor : 0
Backend connection time : 2025-06-24 10:53:42
Client connection time : 2025-06-24 10:53:42
Client idle duration : 0
Client disconnection time : 2025-06-24 10:55:37
Pool Counter : 1
Backend PID : 1336573
Connected : 0
PID : 1336544
Backend ID : 0
Status : Wait for connection
Load balance node : 0
client_host : 192.168.10.11
client_port : 39162
statement : DISCARD ALL
Database : test
Username : t-ishii
Start time : 2025-06-24 10:53:35 (4:33 before process restarting)
Client connection count : 1
Major : 3
Minor : 0
Backend connection time : 2025-06-24 10:53:42
Client connection time : 2025-06-24 10:53:42
Client idle duration : 0
Client disconnection time : 2025-06-24 10:55:37
Pool Counter : 1
Backend PID : 1336574
Connected : 0
PID : 1336544
Backend ID : 1
Status : Wait for connection
Load balance node : 0
client_host : 192.168.10.11
client_port : 39162
statement :
see? so much prettier with labels. the --verbose flag is the glow-up fr fr. β¨
okay that's the whole page bestie, go forth and inspect those processes π
this little love letter comes to you from pgpool-II 4.7.2, dated 2023, and it lives in section 1 of the manual. mwah. πππ¦
π¦ where this page comes from
- ubuntu stonking: pgpool2 4.7.2-1build1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms