[Bug] Refresh append-only materialized view with index

[roseduan]

Apache Cloudberry version

main

What happened

postgres=# REFRESH MATERIALIZED VIEW matview_test;
ERROR: could not open relation with OID 0 (seg0 127.0.0.1:7002 pid=30712)
DETAIL: This can be validly caused by a concurrent delete operation on this object.

What you think should happen instead

No response

How to reproduce

set default_table_access_method TO AO_ROW;

CREATE TABLE events
(
    id           bigint NOT NULL,
    user_id      bigint
);
insert into events values (1, 1), (2, 1), (3, 2), (4, 2), (5, 3), (6, 3), (7, 4), (8, 4), (9, 5), (10, 5);

CREATE MATERIALIZED VIEW matview_test AS SELECT * FROM events WHERE id < 6;
CREATE INDEX idxmatview_test ON matview_test USING btree (user_id);

BEGIN;
UPDATE events SET id = id WHERE id = 1;
UPDATE events SET id = id WHERE id = 2;
UPDATE events SET id = id WHERE id = 3;
COMMIT;

VACUUM events;

REFRESH MATERIALIZED VIEW matview_test;

Operating System

CentOS 7

Anything else

No response

Are you willing to submit PR?

• Yes, I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct.

[github-actions]

Hi, @roseduan welcome!🎊 Thanks for taking the time to point this out.🙌

[avamingli]

I tested this on tag 1.5.0 and found that the issue also exists there. It has been present since our open-source release, indicating that it’s a real bug that has existed for a long time.

[avamingli]

Fix in #866