database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-10-29 22:49:41 +03:00
Code Activity

test_ddl_deparse: Don't use pg_class as source for a matview

Browse Source 
Doing so causes a pg_upgrade of a database containing these objects to
fail whenever pg_class changes.  And it's pointless anyway: we have more
interesting tables anyhow.

Discussion: https://postgr.es/m/CAD5tBc+s8pW9WvH2+_z=B4x95FD4QuzZKcaMpff_9H4rS0VU1A@mail.gmail.com
This commit is contained in:
Alvaro Herrera
2018-03-15 09:51:12 -03:00
parent 8e3f3ab5b8
commit 91797fa438
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/test/modules/test_ddl_deparse/expected/matviews.out
View File

@@ -2,7 +2,7 @@
-- Materialized views -- Materialized views
-- --
CREATE MATERIALIZED VIEW pg_class_mv AS CREATE MATERIALIZED VIEW pg_class_mv AS
SELECT * FROM pg_class LIMIT 1 WITH NO DATA; SELECT * FROM datatype_table LIMIT 1 WITH NO DATA;
NOTICE: DDL test: type simple, tag CREATE MATERIALIZED VIEW NOTICE: DDL test: type simple, tag CREATE MATERIALIZED VIEW
REFRESH MATERIALIZED VIEW pg_class_mv; REFRESH MATERIALIZED VIEW pg_class_mv;
NOTICE: DDL test: type simple, tag REFRESH MATERIALIZED VIEW NOTICE: DDL test: type simple, tag REFRESH MATERIALIZED VIEW

2
src/test/modules/test_ddl_deparse/sql/matviews.sql
View File

@@ -3,6 +3,6 @@
-- --
CREATE MATERIALIZED VIEW pg_class_mv AS CREATE MATERIALIZED VIEW pg_class_mv AS
SELECT * FROM pg_class LIMIT 1 WITH NO DATA; SELECT * FROM datatype_table LIMIT 1 WITH NO DATA;
REFRESH MATERIALIZED VIEW pg_class_mv; REFRESH MATERIALIZED VIEW pg_class_mv;