Re: Implementing Incremental View Maintenance
От | legrand legrand |
---|---|
Тема | Re: Implementing Incremental View Maintenance |
Дата | |
Msg-id | 1577490124579-0.post@n3.nabble.com обсуждение исходный текст |
Ответ на | Re: Implementing Incremental View Maintenance (Takuma Hoshiai <hoshiai@sraoss.co.jp>) |
Ответы |
Re: Implementing Incremental View Maintenance
Re: Implementing Incremental View Maintenance |
Список | pgsql-hackers |
Hello, Thank you for this patch. I have tried to use an other patch with yours: "Planning counters in pg_stat_statements (using pgss_store)" https://www.postgresql.org/message-id/CAOBaU_Y12bn0tOdN9RMBZn29bfYYH11b2CwKO1RO7dX9fQ3aZA%40mail.gmail.com setting shared_preload_libraries='pg_stat_statements' pg_stat_statements.track=all and creating the extension When trying following syntax: create table b1 (id integer, x numeric(10,3)); create incremental materialized view mv1 as select id, count(*),sum(x) from b1 group by id; insert into b1 values (1,1) I got an ASSERT FAILURE in pg_stat_statements.c on Assert(query != NULL); comming from matview.c refresh_matview_datafill(dest_old, query, queryEnv, NULL); or refresh_matview_datafill(dest_new, query, queryEnv, NULL); If this (last) NULL field was replaced by the query text, a comment or just "n/a", it would fix the problem. Could this be investigated ? Thanks in advance Regards PAscal -- Sent from: https://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html
В списке pgsql-hackers по дате отправления: