From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: In pg_dump, split "dump" into "dump" and "dump_contains" |
Date: | 2016-04-07 01:45:51 |
Message-ID: | E1anz15-0007pw-DT@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
In pg_dump, split "dump" into "dump" and "dump_contains"
Historically, the "dump" component of the namespace has been used
to decide if the objects inside of the namespace should be dumped
also. Given that "dump" is now a bitmask and may be partial, and
we may want to dump out all components of the namespace object but
only some of the components of objects contained in the namespace,
create a "dump_contains" bitmask which will represent what components
of the objects inside of a namespace should be dumped out.
No behavior change here, but in preparation for a change where we
will dump out just the ACLs of objects in pg_catalog, but we might
not dump out the ACL of the pg_catalog namespace itself (for instance,
when it hasn't been changed from the value set at initdb time).
Reviews by Alexander Korotkov, Jose Luis Tallon
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/d217b2c360cb9a746b4ef122c568bdfedb6d726e
Modified Files
--------------
src/bin/pg_dump/pg_dump.c | 23 +++++++++++++----------
src/bin/pg_dump/pg_dump.h | 3 ++-
2 files changed, 15 insertions(+), 11 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2016-04-07 01:59:43 | Re: pgsql: Use GRANT system to manage access to sensitive functions |
Previous Message | Magnus Hagander | 2016-04-06 16:41:46 | Re: pgsql: Implement backup API functions for non-exclusive backups |