Use `deparse` schema for deparse event trigger code
authorIan Barwick <ian@2ndquadrant.com>
Mon, 15 Dec 2014 04:24:43 +0000 (13:24 +0900)
committerIan Barwick <ian@2ndquadrant.com>
Mon, 15 Dec 2014 04:24:43 +0000 (13:24 +0900)
commit6bd07b3176a74a3908a7b413d7e2740a06135676
tree2e8be688ca01e010790fe414195aab9b6a81cd28
parent585f264a8e6bccaa244718360bac148dfbf91da9
Use `deparse` schema for deparse event trigger code

The definitions for the deparse event trigger code won't of
course be deparsed themselves, so we don't want to dump them.
By using a separate schema, it's easier to exclude them from
the dump output.
src/test/regress/ddl-deparse/dump_regress_db.pl
src/test/regress/ddl-deparse/input/create_function.source
src/test/regress/ddl-deparse/input/deparse_init.source
src/test/regress/ddl-deparse/input/deparse_test.source
src/test/regress/ddl-deparse/output/create_function.source
src/test/regress/ddl-deparse/output/deparse_init.source
src/test/regress/ddl-deparse/output/deparse_test.source
src/test/regress/ddl-deparse/regress.c