diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-11-29 12:13:12 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-11-29 12:13:12 -0500 |
| commit | 4f33af23e7e3ac30b3cb9480981c3accf401ef01 (patch) | |
| tree | 886c1cdf3c88645be25642e534e8124d2fdc72dc | |
| parent | e04a8059a74c125a8af94acdcb7b15b92188470a (diff) | |
| download | postgresql-4f33af23e7e3ac30b3cb9480981c3accf401ef01.tar.gz postgresql-4f33af23e7e3ac30b3cb9480981c3accf401ef01.zip | |
Doc: improve documentation about ORDER BY in matviews.
Remove the confusing use of ORDER BY in an example materialized
view. It adds nothing to the example, but might encourage
people to follow bad practice. Clarify REFRESH MATERIALIZED
VIEW's note about whether view ordering is retained (it isn't).
Maciek Sakrejda
Discussion: https://postgr.es/m/CAOtHd0D-OvrUU0C=4hX28p4BaSE1XL78BAQ0VcDaLLt8tdUzsg@mail.gmail.com
| -rw-r--r-- | doc/src/sgml/ref/refresh_materialized_view.sgml | 10 | ||||
| -rw-r--r-- | doc/src/sgml/rules.sgml | 3 |
2 files changed, 4 insertions, 9 deletions
diff --git a/doc/src/sgml/ref/refresh_materialized_view.sgml b/doc/src/sgml/ref/refresh_materialized_view.sgml index 3bf88844478..675d6090f3c 100644 --- a/doc/src/sgml/ref/refresh_materialized_view.sgml +++ b/doc/src/sgml/ref/refresh_materialized_view.sgml @@ -93,12 +93,10 @@ REFRESH MATERIALIZED VIEW [ CONCURRENTLY ] <replaceable class="parameter">name</ <title>Notes</title> <para> - While the default index for future - <link linkend="sql-cluster"><command>CLUSTER</command></link> - operations is retained, <command>REFRESH MATERIALIZED VIEW</command> does not - order the generated rows based on this property. If you want the data - to be ordered upon generation, you must use an <literal>ORDER BY</literal> - clause in the backing query. + If there is an <literal>ORDER BY</literal> clause in the materialized + view's defining query, the original contents of the materialized view + will be ordered that way; but <command>REFRESH MATERIALIZED + VIEW</command> does not guarantee to preserve that ordering. </para> </refsect1> diff --git a/doc/src/sgml/rules.sgml b/doc/src/sgml/rules.sgml index 6065b1c2a31..4aa4e00e017 100644 --- a/doc/src/sgml/rules.sgml +++ b/doc/src/sgml/rules.sgml @@ -962,9 +962,6 @@ CREATE MATERIALIZED VIEW sales_summary AS WHERE invoice_date < CURRENT_DATE GROUP BY seller_no, - invoice_date - ORDER BY - seller_no, invoice_date; CREATE UNIQUE INDEX sales_summary_seller |