Re: Incremental View Maintenance, take 2

Поиск
Список
Период
Сортировка
Искать
От
jian he
Тема
Re: Incremental View Maintenance, take 2
Дата
Msg-id
CACJufxF-HGe9zLaGaSryeYVq9abz2FyKKtdgghNWktkjnFXOJQ@mail.gmail.com
Ответ на
Список
Дерево обсуждения
Re: Incremental View Maintenance, take 2 Alexandre Felipe <o.alexandre.felipe@gmail.com>
Re: Incremental View Maintenance, take 2 Andreas Karlsson <andreas@proxel.se>
Re: Incremental View Maintenance, take 2 Alexandre Felipe <o.alexandre.felipe@gmail.com>
Re: Incremental View Maintenance, take 2 Álvaro Herrera <alvherre@kurilemu.de>
Re: Incremental View Maintenance, take 2 Alexandre Felipe <o.alexandre.felipe@gmail.com>
Re: Incremental View Maintenance, take 2 Alexandre Felipe <o.alexandre.felipe@gmail.com>
Re: Incremental View Maintenance, take 2 Yugo Nagata <nagata@sraoss.co.jp>
Re: Incremental View Maintenance, take 2 (design considerations) Yugo Nagata <nagata@sraoss.co.jp>
ok. Now I really found a small bug.

this works as intended:
BEGIN;
CREATE INCREMENTAL MATERIALIZED VIEW test_ivm AS SELECT i, MIN(j) as
min_j  FROM mv_base_a group by 1;
INSERT INTO mv_base_a select 1,-2 where false;
rollback;

however the following one:
BEGIN;
CREATE INCREMENTAL MATERIALIZED VIEW test_ivm1 AS SELECT MIN(j) as
min_j  FROM mv_base_a;
INSERT INTO mv_base_a  select 1, -2 where false;
rollback;

will evaluate
tuplestore_tuple_count(new_tuplestores) to 1, it will walk through
IVM_immediate_maintenance function to apply_delta.
but should it be zero?


В списке pgsql-hackers по дате отправления
От: Miroslav Bendik
Дата:
FAQ