By the way On 4/17/2019 7:26, laurent.decha...@orange.com wrote:
I can see whether there is parallelism with pg_top or barely top on the server.<DBEAVER> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 38584 postgres 20 0 8863828 8.153g 8.151g R 100.0 3.2 1:23.01 postgres 10 root 20 0 0 0 0 S 0.3 0.0 88:07.26 rcu_sched <BASIC JDBC> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 46687 postgres 20 0 8864620 0.978g 0.977g S 38.5 0.4 0:01.16 postgres 46689 postgres 20 0 8864348 996.4m 995.1m R 38.5 0.4 0:01.16 postgres 46690 postgres 20 0 8864348 987.2m 985.8m S 38.5 0.4 0:01.16 postgres 46691 postgres 20 0 8864348 998436 997084 R 38.5 0.4 0:01.16 postgres ... 46682 postgres 20 0 157996 2596 1548 R 0.7 0.0 0:00.05 top
If you just use top with the -c option, you will see each postgres process identify itself as to its role, e.g.
postgres: parallel worker for PID 46687 or postgres: SELECT ... or postgres: wal writer extremely useful this. -Gunther
