pgsql: Rethink order of operations for dumping extension member objects

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Rethink order of operations for dumping extension member objects
Date: 2011-02-09 19:06:03
Message-ID: E1PnFMZ-0001Ic-Gb@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Rethink order of operations for dumping extension member objects.

My original idea of doing extension member identification during
getDependencies() didn't work correctly: we have to mark member tables as
not-to-be-dumped rather earlier than that, else their subsidiary objects
like indexes get dumped anyway. Rearrange code to mark them early enough.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/183d3cff850eee12357b8b4a8c5e62362ba5d8cc

Modified Files
--------------
src/bin/pg_dump/common.c | 38 +++++---
src/bin/pg_dump/pg_dump.c | 236 +++++++++++++++++++++++++++++++--------------
src/bin/pg_dump/pg_dump.h | 4 +-
3 files changed, 190 insertions(+), 88 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2011-02-09 21:30:32 pgsql: Information schema views for collation support
Previous Message Tom Lane 2011-02-09 16:57:03 pgsql: Implement "ALTER EXTENSION ADD object".