Hi Peter,
On 2018-02-28 16:50:44 +0000, Phil Florent wrote:
> With an index creation (create index t1_i1 on t1(c1, c2);) I have this kind of output :
>
> ./t -d 20 -o "pid, backend_type, query, wait_event_type, wait_event"
> busy_pc | distinct_exe | pid | backend_type | query | wait_event_type | wait_event
>
---------+--------------+------+----------------+-----------------------------------+-----------------+--------------
> 68 | 1 / 136 | 8262 | client backend | create index t1_i1 on t1(c1, c2); | IO | DataFileRead
> 26 | 1 / 53 | 8262 | client backend | create index t1_i1 on t1(c1, c2); | |
> 6 | 1 / 11 | 8262 | client backend | create index t1_i1 on t1(c1, c2); | IO | BufFileWrite
> (3 rows)
> No parallel worker. At least one parallel worker was active though, I could see its work with a direct query on
pg_stat_activityor a ps -ef :
>
> ...
> postgres 8262 8230 7 08:54 ? 00:22:46 postgres: 11/main: postgres postgres [local] CREATE INDEX
> ...
> postgres 9833 8230 23 14:17 ? 00:00:33 postgres: 11/main: parallel worker for PID 8262
> ...
Looks like we're not doing a pgstat_report_activity() in the workers?
Any argument for not doing so?
Greetings,
Andres Freund