Choose live views or stored query results ​

An ordinary Coordinator DB view stores a SELECT definition. Reading the view evaluates that definition against its sources; it does not queue an asynchronous insert or maintain a separate result table. Materialized views and automatic refresh schedules are unavailable.

CREATE TABLE view_orders(id INTEGER PRIMARY KEY, amount INTEGER);
INSERT INTO view_orders VALUES (1, 40), (2, 60);
CREATE VIEW order_amounts AS
SELECT id, amount FROM view_orders WHERE amount > 0;

SELECT * FROM order_amounts ORDER BY id;

A later committed change to view_orders is read by subsequent view queries according to their normal transaction context. There is no refresh command to wait for.

When a report needs stored result rows, create a separate table with CREATE TABLE ... AS SELECT. That table is an independent copy; later source writes do not update it. The application must explicitly replace or adjust its rows and define when that work is considered complete. Use a transaction if several statements must commit together, and verify the stored totals against the source query after maintenance.

See CREATE VIEW, CREATE TABLE and transactions.