Fix handling of REFRESH MATERIALIZED VIEW CONCURRENTLY
authorPavan Deolasee <pavan.deolasee@gmail.com>
Tue, 17 Jul 2018 04:47:40 +0000 (10:17 +0530)
committerPavan Deolasee <pavan.deolasee@gmail.com>
Tue, 17 Jul 2018 04:47:40 +0000 (10:17 +0530)
commit47e01d7befddbe6c345858623d556ddc64203993
treee132f6673cd773d515b8b8deac44d6acdc30cc75
parented8a5685d65bbe8096f28a91b2f178e79ab083e0
Fix handling of REFRESH MATERIALIZED VIEW CONCURRENTLY

We create a coordinator-only LOCAL temporary table for REFRESH MATERIALIZED
VIEW CONCURRENTLY. Since this table does not exist on the remote nodes, we must
not use explicit "ANALYZE <temptable>". Instead, just analyze it locally like
we were doing at other places.

Restore the matview test case to use REFRESH MATERIALIZED VIEW CONCURRENTLY now
that the underlying bug is fixed.
src/backend/commands/matview.c
src/test/regress/expected/matview.out
src/test/regress/sql/matview.sql