Re: Incremental View Maintenance, take 2 - Mailing list pgsql-hackers

From jian he
Subject Re: Incremental View Maintenance, take 2
Date
Msg-id CACJufxF-HGe9zLaGaSryeYVq9abz2FyKKtdgghNWktkjnFXOJQ@mail.gmail.com
Whole thread Raw
In response to Re: Incremental View Maintenance, take 2  (jian he <jian.universality@gmail.com>)
Responses Re: Incremental View Maintenance, take 2
List pgsql-hackers
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 by date:

Previous
From: Thomas Munro
Date:
Subject: Re: possible bug in handling of contrecords in dd38ff28ad (Fix recovery_prefetch with low maintenance_io_concurrency)
Next
From: Miroslav Bendik
Date:
Subject: Re: Incremental sort for access method with ordered scan support (amcanorderbyop)