From 549dae0352a06a43ec664dc158556e12ec2d30e5 Mon Sep 17 00:00:00 2001
From: Kevin Grittner
Date: Fri, 22 Mar 2013 13:27:34 -0500
Subject: Fix problems with incomplete attempt to prohibit OIDS with MVs.
Problem with assertion failure in restoring from pg_dump output
reported by Joachim Wieland.
Review and suggestions by Tom Lane and Robert Haas.
---
doc/src/sgml/ref/create_materialized_view.sgml | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
(limited to 'doc/src')
diff --git a/doc/src/sgml/ref/create_materialized_view.sgml b/doc/src/sgml/ref/create_materialized_view.sgml
index ed3bb4d3ae5..a7e4e210eeb 100644
--- a/doc/src/sgml/ref/create_materialized_view.sgml
+++ b/doc/src/sgml/ref/create_materialized_view.sgml
@@ -44,6 +44,9 @@ CREATE [ UNLOGGED ] MATERIALIZED VIEW table_name
CREATE MATERIALIZED VIEW is similar to
CREATE TABLE AS>, except that it also remembers the query used
to initialize the view, so that it can be refreshed later upon demand.
+ A materialized view has many of the same properties as a table, but there
+ is no support for temporary materialized views or automatic generation of
+ OIDs.
@@ -88,7 +91,9 @@ CREATE [ UNLOGGED ] MATERIALIZED VIEW table_name
This clause specifies optional storage parameters for the new
materialized view; see for more
- information.
+ information. All parameters supported for CREATE
+ TABLE are also supported for CREATE MATERIALIZED
+ VIEW with the exception of OIDS.
See for more information.
--
cgit v1.2.3