pgsql: Fix ordering of obj id for Rules and EventTriggers in pg_dump.

From: Joe Conway <mail(at)joeconway(dot)com>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix ordering of obj id for Rules and EventTriggers in pg_dump.
Date: 2013-06-10 00:32:46
Message-ID: E1Ulq2Q-0004V1-Rx@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/33a4466f767be8b153ef1ef78433ad9b1867dab8

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

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2013-06-10 18:04:11 pgsql: Fix pg_isready to handle conninfo properly.
Previous Message Joe Conway 2013-06-10 00:32:34 pgsql: Fix ordering of obj id for Rules and EventTriggers in pg_dump.