Philip Semanchuk <[email protected]> writes:
> I can confirm that it’s not waiting on a lock. In addition, through the AWS
> CPU utilization monitor I can see that the REFRESH uses one CPU/worker
> whereas the CREATE uses four. This is consistent with the EXPLAIN ANALYZE for
> the CREATE which says it uses four workers.
Hm. I tried to reproduce this here, and in a simple test case I get
parallelized plans for both CREATE and REFRESH. Are you sure the
REFRESH is running with the same server parameter settings?
>> also, can you share the plans where you see the diff.
> Unless I misunderstand, there is no plan for a REFRESH.
EXPLAIN isn't bright about that, but if you enable auto_explain,
it will log the plan for a REFRESH's query.
regards, tom lane