pgsql: Fix ordering of obj id for Rules and EventTriggers in pg_dump. - Mailing list pgsql-committers

From Joe Conway
Subject pgsql: Fix ordering of obj id for Rules and EventTriggers in pg_dump.
Date
Msg-id E1Ulq23-0004UD-3h@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix ordering of obj id for Rules and EventTriggers in pg_dump.

getSchemaData() must identify extension member objects and mark them
as not to be dumped. This must happen after reading all objects that can be
direct members of extensions, but before we begin to process table subsidiary
objects. Both rules and event triggers were wrong in this regard.

Backport rules portion of patch to 9.1 -- event triggers do not exist prior to 9.3.
Suggested fix by Tom Lane, initial complaint and patch by me.

Branch
------
REL9_1_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/86742ac9c838cb383f951703f28938d371cb7858

Modified Files
--------------
src/bin/pg_dump/common.c |    8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Tweak postgres_fdw regression test so autovacuum doesn't change
Next
From: Joe Conway
Date:
Subject: pgsql: Fix ordering of obj id for Rules and EventTriggers in pg_dump.