rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Suppress extensions in partial dumps. 

We initially had pg_dump emit CREATE EXTENSION commands unconditionally.
However, pg_dump has long been in the habit of not dumping procedural
language definitions when a --schema or --table switch is given.  It seems
appropriate to handle extensions the same way, since like PLs they are SQL
objects that are not in any particular schema.  Per complaint from Adrian
Schreyer.
This commit is contained in:
Tom Lane 2011-05-25 16:26:45 -04:00
parent 3439e40f9a
commit 7b158d1bae
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
src/bin/pg_dump/pg_dump.c
View File

@ -1153,10 +1153,11 @@ selectDumpableDefaultACL(DefaultACLInfo *dinfo)
* selectDumpableExtension: policy-setting subroutine
* Mark an extension as to be dumped or not
*
* Normally, we just dump all extensions. However, in binary-upgrade mode
* it's necessary to skip built-in extensions, since we assume those will
* already be installed in the target database. We identify such extensions
* by their having OIDs in the range reserved for initdb.
* Normally, we dump all extensions, or none of them if include_everything
* is false (i.e., a --schema or --table switch was given). However, in
* binary-upgrade mode it's necessary to skip built-in extensions, since we
* assume those will already be installed in the target database. We identify
* such extensions by their having OIDs in the range reserved for initdb.
*/
static void
selectDumpableExtension(ExtensionInfo *extinfo)
@ -1164,7 +1165,7 @@ selectDumpableExtension(ExtensionInfo *extinfo)
if (binary_upgrade && extinfo->dobj.catId.oid < (Oid) FirstNormalObjectId)
extinfo->dobj.dump = false;
else
extinfo->dobj.dump = true;
extinfo->dobj.dump = include_everything;
}
/*