From 5e45211a64149b3c659b90ff2de6fa982a5a93ed Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:17:33 +0200 Subject: Adding upstream version 15.5. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/sql-refreshmaterializedview.html | 59 ++++++++++++++++++++++ 1 file changed, 59 insertions(+) create mode 100644 doc/src/sgml/html/sql-refreshmaterializedview.html (limited to 'doc/src/sgml/html/sql-refreshmaterializedview.html') diff --git a/doc/src/sgml/html/sql-refreshmaterializedview.html b/doc/src/sgml/html/sql-refreshmaterializedview.html new file mode 100644 index 0000000..b33122b --- /dev/null +++ b/doc/src/sgml/html/sql-refreshmaterializedview.html @@ -0,0 +1,59 @@ + +REFRESH MATERIALIZED VIEW
REFRESH MATERIALIZED VIEW
Prev UpSQL CommandsHome Next

REFRESH MATERIALIZED VIEW

REFRESH MATERIALIZED VIEW — replace the contents of a materialized view

Synopsis

+REFRESH MATERIALIZED VIEW [ CONCURRENTLY ] name
+    [ WITH [ NO ] DATA ]
+

Description

+ REFRESH MATERIALIZED VIEW completely replaces the + contents of a materialized view. To execute this command you must be the + owner of the materialized view. The old contents are discarded. If + WITH DATA is specified (or defaults) the backing query + is executed to provide the new data, and the materialized view is left in a + scannable state. If WITH NO DATA is specified no new + data is generated and the materialized view is left in an unscannable + state. +

+ CONCURRENTLY and WITH NO DATA may not + be specified together. +

Parameters

CONCURRENTLY

+ Refresh 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 resources and complete more quickly, + but could block other connections which are trying to read from the + materialized view. This option may be faster in cases where a small + number of rows are affected. +

+ This option is only allowed if there is at least one + UNIQUE index on the materialized view which uses only + column names and includes all rows; that is, it must not be an + expression index or include a WHERE clause. +

+ This option may not be used when the materialized view is not already + populated. +

+ Even with this option only one REFRESH at a time may + run against any one materialized view. +

name

+ The name (optionally schema-qualified) of the materialized view to + refresh. +

Notes

+ If there is an ORDER BY clause in the materialized + view's defining query, the original contents of the materialized view + will be ordered that way; but REFRESH MATERIALIZED + VIEW does not guarantee to preserve that ordering. +

Examples

+ This command will replace the contents of the materialized view called + order_summary using the query from the materialized + view's definition, and leave it in a scannable state: +

+REFRESH MATERIALIZED VIEW order_summary;
+

+

+ This command will free storage associated with the materialized view + annual_statistics_basis and leave it in an unscannable + state: +

+REFRESH MATERIALIZED VIEW annual_statistics_basis WITH NO DATA;
+

Compatibility

+ REFRESH MATERIALIZED VIEW is a + PostgreSQL extension. +

Prev Up Next
REASSIGN OWNED Home REINDEX
\ No newline at end of file -- cgit v1.2.3