Clarify info about WITH NO DATA parameter (github#969)

* Clarify info about WITH NO DATA parameter * Update api/create_materialized_view.md Co-authored-by: Charis <[email protected]> Co-authored-by: Charis <[email protected]>
jnidzwetzki · Apr 4, 2022 · 215c8cd · 215c8cd
1 parent c308679
commit 215c8cd
Showing 1 changed file with 7 additions and 3 deletions.
diff --git a/api/create_materialized_view.md b/api/create_materialized_view.md
@@ -22,8 +22,12 @@ GROUP BY time_bucket( <const_value>, <partition_col_of_hypertable> ),
 [HAVING ...]
 ```
 
-The continuous aggregate view is automatically refreshed unless `WITH NO DATA`
-is given. This setting defaults to `WITH DATA`. For more information, see
+The continuous aggregate view defaults to `WITH DATA`. This means that when the
+view is created, it refreshes using all the current data in its underlying
+hypertable. This occurs once when the view is created. If you want the view to
+be refreshed regularly, you can use a refresh policy. If you do not want the
+view to update when it is first created, use the `WITH NO DATA`
+parameter. For more information, see
 [`refresh_continuous_aggregate`][refresh-cagg].
 
 Continuous aggregates have some limitations of what types of queries they can
@@ -45,7 +49,7 @@ Some important things to remember when constructing your `SELECT` query:
     aggregates, but you can run them in a `SELECT` query from the continuous
     aggregate view.
 *   You can usually use aggregates that are
-    [parallelized by PostgreSQL][postgres-parallel-agg] in the view definition, 
+    [parallelized by PostgreSQL][postgres-parallel-agg] in the view definition,
     including most aggregates distributed by PostgreSQL. However, the `ORDER BY`,
     `DISTINCT` and `FILTER` clauses are not supported.
 *   All functions and their arguments included in `SELECT`, `GROUP BY` and