Re: Inconsistency with EXPLAIN ANALYZE CREATE MATERIALIZED VIEW

On Tue, 6 Aug 2024 at 21:06, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> wrote:
>
> On Thu, 1 Aug 2024 23:41:18 +0500
> Kirill Reshke <reshkekirill(at)gmail(dot)com> wrote:
>
> > On Thu, 1 Aug 2024 at 23:27, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> > > Relatedly, if we can EXPLAIN a CREATE MATERIALIZED VIEW, perhaps we
> > > should be able to EXPLAIN a REFRESH MATERIALIZED VIEW, too?
> > Sure
>
> REFRESH MATERIALIZED VIEW consists of not only the view query
> execution in refresh_matview_datafill but also refresh_by_heap_swap
> or refresh_by_match_merge. The former doesn't execute any query, so
> it would not a problem, but the latter executes additional queries
> including SELECT, some DDL, DELETE, and INSERT.
>
> If we would make EXPLAIN support REFRESH MATERIALIZED VIEW CONCURRENTLY
> command, how should we handle these additional queries?
>
> Regards,
> Yugo Nagata
>
> --
> Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>

Hmm, is it a big issue? Maybe we can just add them in proper places of
output the same way we do it with triggers?

--
Best regards,
Kirill Reshke