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

2018-03-15 Thread Alvaro Herrera
test_ddl_deparse: Don't use pg_class as source for a matview 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=b4x95fd4quz

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

2018-03-15 Thread Alvaro Herrera
test_ddl_deparse: Don't use pg_class as source for a matview 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=b4x95fd4quz

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

2018-03-15 Thread Alvaro Herrera
test_ddl_deparse: Don't use pg_class as source for a matview 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=b4x95fd4quz

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

2018-03-15 Thread Alvaro Herrera
test_ddl_deparse: Don't use pg_class as source for a matview 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=b4x95fd4quz