diff options
| author | Tom Lane | 2013-05-06 17:26:51 +0000 |
|---|---|---|
| committer | Tom Lane | 2013-05-06 17:27:22 +0000 |
| commit | 1d6c72a55b23554cfb946527dc77f9d80044ae2c (patch) | |
| tree | 8f7964a0114022585c1a0d90f37d2fd466bb6154 /src/test/regress/expected/rules.out | |
| parent | 5da5798004e90b14332918e7db702271442d465d (diff) | |
Move materialized views' is-populated status into their pg_class entries.
Previously this state was represented by whether the view's disk file had
zero or nonzero size, which is problematic for numerous reasons, since it's
breaking a fundamental assumption about heap storage. This was done to
allow unlogged matviews to revert to unpopulated status after a crash
despite our lack of any ability to update catalog entries post-crash.
However, this poses enough risk of future problems that it seems better to
not support unlogged matviews until we can find another way. Accordingly,
revert that choice as well as a number of existing kluges forced by it
in favor of creating a pg_class.relispopulated flag column.
Diffstat (limited to 'src/test/regress/expected/rules.out')
| -rw-r--r-- | src/test/regress/expected/rules.out | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/test/regress/expected/rules.out b/src/test/regress/expected/rules.out index a4ecfd2aeac..dc3c8a83812 100644 --- a/src/test/regress/expected/rules.out +++ b/src/test/regress/expected/rules.out @@ -1347,7 +1347,7 @@ SELECT viewname, definition FROM pg_views WHERE schemaname <> 'information_schem | pg_get_userbyid(c.relowner) AS matviewowner, + | t.spcname AS tablespace, + | c.relhasindex AS hasindexes, + - | pg_relation_is_scannable(c.oid) AS isscannable, + + | c.relispopulated AS ispopulated, + | pg_get_viewdef(c.oid) AS definition + | FROM ((pg_class c + | LEFT JOIN pg_namespace n ON ((n.oid = c.relnamespace))) + |
