Re: Implementing Incremental View Maintenance
От | legrand legrand |
---|---|
Тема | Re: Implementing Incremental View Maintenance |
Дата | |
Msg-id | 1577046170225-0.post@n3.nabble.com обсуждение исходный текст |
Ответ на | Re: Implementing Incremental View Maintenance (Yugo Nagata <nagata@sraoss.co.jp>) |
Ответы |
RE: Implementing Incremental View Maintenance
|
Список | pgsql-hackers |
Hello, First of all many thanks for this Great feature replacing so many triggers by a so simple syntax ;o) I was wondering about performances and add a look at pg_stat_statements (with track=all) with IVM_v9.patch. For each insert into a base table there are 3 statements: - ANALYZE pg_temp_3.pg_temp_81976 - WITH updt AS ( UPDATE public.mv1 AS mv SET __ivm_count__ = ... - DROP TABLE pg_temp_3.pg_temp_81976 It generates a lot of lines in pg_stat_statements with calls = 1. Thoses statements can not be shared because the temp table is dropped each time. Is there a plan to change this ? Many Thanks again Regards PAscal -- Sent from: https://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html
В списке pgsql-hackers по дате отправления: