ORDER BY in materialized view example?
Maciek Sakrejda <m.sakrejda@gmail.com>
From: Maciek Sakrejda <m.sakrejda@gmail.com>
To: pgsql-docs@postgresql.org
Date: 2021-11-23T06:18:46Z
Lists: pgsql-docs
An example in the materialized view documentation [1] includes an ORDER BY clause without a clear reason. Does it help build the index more efficiently? I suppose it's also sort of like a CLUSTER? But it seems like the ORDER BY should either be explained or dropped: as is, this gives the impression that the ORDER BY can be "embedded" into the resulting relation and persist to other queries that do not include an explicit ORDER BY. (I recently ran across this belief, though not sure if this was due to this example.) Thoughts? [1]: https://www.postgresql.org/docs/current/rules-materializedviews.html
Commits
-
Doc: improve documentation about ORDER BY in matviews.
- ce43b3dc52c9 14.2 landed
- a7359913a1c2 13.6 landed
- 514f0ae4f40f 10.20 landed
- 3f43dcc1c686 11.15 landed
- 2f908e1a3b9c 12.10 landed
- 4f33af23e7e3 15.0 landed