pgsql: In pg_dump, use a bitmap to represent what to include - Mailing list pgsql-committers

From Stephen Frost
Subject pgsql: In pg_dump, use a bitmap to represent what to include
Date
Msg-id E1anz15-0007pu-DL@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
In pg_dump, use a bitmap to represent what to include

pg_dump has historically used a simple boolean 'dump' value to indicate
if a given object should be included in the dump or not.  Instead, use
a bitmap which breaks down the components of an object into their
distinct pieces and use that bitmap to only include the components
requested.

This does not include any behavioral change, but is in preperation for
the change to dump out just ACLs for objects in pg_catalog.

Reviews by Alexander Korotkov, Jose Luis Tallon

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/a9f0e8e5a2e779a888988cb64479a6723f668c84

Modified Files
--------------
src/bin/pg_dump/common.c  |    2 +-
src/bin/pg_dump/pg_dump.c | 1502 ++++++++++++++++++++++++---------------------
src/bin/pg_dump/pg_dump.h |   14 +-
3 files changed, 833 insertions(+), 685 deletions(-)


pgsql-committers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: pgsql: Implement backup API functions for non-exclusive backups
Next
From: Stephen Frost
Date:
Subject: pgsql: In pg_dump, include pg_catalog and extension ACLs, if changed