CREATE/REFRESH MATERIALIZED VIEW planner difference?
Philip Semanchuk <philip@americanefficient.com>
From: Philip Semanchuk <philip@americanefficient.com>
To: PostgreSQL General <pgsql-general@lists.postgresql.org>
Date: 2021-06-01T18:00:16Z
Lists: pgsql-general
Hi all, Should I expect a planner difference between CREATE MATERIALIZED VIEW and REFRESH MATERIALIZED VIEW? We have a materialized view that uses 4 workers during CREATE but only one worker during REFRESH, and as a result the refresh takes much longer (~90 minutes vs. 30 minutes for the CREATE). So far this behavior has been 100% consistent. I'm running both the CREATE and REFRESH on the same server (Postgres 11.9 on AWS Aurora). I don't think the refresh is using one worker in response to other things happening on the server because we’ve observed this happening when the server is not busy. We're not using the CONCURRENTLY option for REFRESH. THanks Philip
Commits
-
Enable parallelism in REFRESH MATERIALIZED VIEW.
- 9e7ccd9ef64d 14.0 cited