PgSQL Processes

PgSQL Processes is a root-administrator page for reviewing active PostgreSQL backend sessions across the server and terminating a problematic backend only when the operational impact is understood.

Where to find it: Open the Server menu and choose PgSQL Processes. Conditional items appear only when their service is installed and available.

Available to: Root only.

What this page does

The page supports live PostgreSQL incident work. It shows active backend sessions, runtime, database role, client host, database, command/state, query details, and a controlled Kill action for sessions that are safe to terminate.

Before you start

PgSQL Processes is an evidence page. Refresh it in the correct scope and correlate the result with the owning service or logs before using a disruptive action.

Why use it — and when not to

Use PgSQL Processes when you need current evidence or a bounded status view. Do not use one snapshot as the only basis for a destructive action; correlate it with time, scope, logs, and the affected service.

How to use it

1. Choose the exact account, domain, service, process, or time range.
2. Refresh the data and read the status in context.
3. Correlate it with logs or a second status source before taking action.
4. If an action is needed, use the smallest supported action and refresh again.

Result and next check

Opening or refreshing PgSQL Processes does not change configuration. If the page offers an action such as kill, clear, retry, or restart, that action has its own impact and must be confirmed separately.