Hi all, In concurrently refreshing materialized view, we check whether that materialized view has suitable index(unique and not having WHERE condition), after filling data to new snapshot (refresh_matview_datafill()). This logic leads to taking a lot of time until postgres returns ERROR log if that table doesn't has suitable index and table is large. it wastes time. I think we should check whether that materialized view can use concurrently refreshing or not in advance. The patch is attached.
Please give me feedbacks. -- Regards, -- Masahiko Sawada
matview_concurrently_refresh_check_index_v1.patch
Description: binary/octet-stream
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
