On Sun, Feb 23, 2025 at 10:21 AM Greg Sabino Mullane wrote:
> This is the correct interpretation. A regular refresh simply runs the query
> and replaces the old view, regardless of the number of rows that have
> changed. A concurrent refresh runs the query and updates the rows in place,
> so it
On Sat, Feb 22, 2025 at 8:58 PM Tobias McNulty
wrote:
> "Without this option a refresh which affects a lot of rows will tend to
> use fewer resources"
...
> either that (1) the refresh operation actually updates the contents of a
> lot of rows in the materialized view
This is the correct inte
Hello,
The documentation [1] for REFRESH MATERIALIZED VIEW states that the
"CONCURRENTLY" parameter:
> Refresh[es] the materialized view without locking out concurrent selects on
> the materialized
> view. Without this option a refresh which affects a lot of rows will tend to
> use fewer
> reso
