SHOW_POOL_PROCESSES(1)
π NAME π
SHOW_POOL_PROCESSES β bestie, this one slides back a whole list of every Pgpool-II process that's just vibing, waiting for connections, or actively dealing with one.
β¨ SYNOPSIS β¨
SHOW POOL_PROCESSES
πΈ DESCRIPTION πΈ
okay so SHOW_POOL_PROCESSES sends back a list of all the Pgpool-II processes that are waiting for connections and dealing with a connection. that's it, that's the whole job. icon behavior honestly.
it's giving 8 columns, and here they are, no skipping:
pool_pidβ the PID of the Pgpool-II process that's on display. that's its whole government name.start_timeβ the timestamp of when this process was launched. it's the process's birthday, basically π- if
child_life_timeis set to not0, the time before process restarting gets displayed too. (yes, "is set not 0" β that's the original wording, i don't make the rules π )
- if
client_connection_countβ counts the number of times this process has been used by clients. how many times the girlies came through.databaseβ the database name of the currently active backend for this process.usernameβ the user name used in the connection of the currently active backend for this process.backend_connection_timeβ the creation time and date of the connection.pool_counterβ counts the number of times this pool of connections (the process) has been used by clients. lowkey the same energy asclient_connection_countbut for the whole pool, and yes they both live here, we don't question it.statusβ current status of this process. possible values are:- Execute command: Executing a command.
- Idle: The process is waiting for a new client command.
- Idle: The process is waiting for a new client command in a transaction.
- Wait for connection: The process is waiting for a new client connection.
the Idle status shows up twice on purpose, bestie β one for plain idle, one for idle inside a transaction. don't come for me, that's just what the page says π«Ά
π¦ here's a lil example session π¦
test=# show pool_processes;
pool_pid | start_time | client_connection_count | database | username | backend_connection_time | pool_counter | status
----------+------------------------------------------------------+-------------------------+----------+----------+-------------------------+--------------+---------------------
32641 | 2021-09-28 04:40:45 | 0 | | | | | Wait for connection
32642 | 2021-09-28 04:40:45 | 0 | | | | | Wait for connection
32643 | 2021-09-28 04:40:45 | 0 | test | kawamoto | 2021-09-28 04:40:48 | 1 | Idle
32644 | 2021-09-28 04:40:45 | 0 | test | kawamoto | 2021-09-28 04:43:15 | 1 | Execute command
32645 | 2021-09-28 04:40:45 | 0 | | | | | Wait for connection
32646 | 2021-09-28 04:40:45 | 0 | | | | | Wait for connection
32647 | 2021-09-28 04:40:45 | 0 | | | | | Wait for connection
32648 | 2021-09-28 04:40:45 (3:15 before process restarting) | 2 | | | | | Wait for connection
(8 rows)
look at that last row staying booked and busy with (3:15 before process restarting) β she's counting down her own rest, main character energy fr fr π
β¨ that's the whole page bestie, we ate and left no crumbs β¨
this was pgpool-II 4.7.2 Documentation for the SHOW_POOL_PROCESSES(1) page, dated 2023. mwah, go query something ππΈβ¨
π¦ 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