In dumpTable, re-instate the skipping logic
Pretty sure I removed this based on some incorrect thinking that it was no longer possible to reach this point for a table which will not be dumped, but that's clearly wrong. Pointed out on IRC by Erik Rijkers.
This commit is contained in:
parent
8b99edefca
commit
689f9a0588
@ -14846,6 +14846,13 @@ dumpTable(Archive *fout, TableInfo *tbinfo)
|
|||||||
DumpOptions *dopt = fout->dopt;
|
DumpOptions *dopt = fout->dopt;
|
||||||
char *namecopy;
|
char *namecopy;
|
||||||
|
|
||||||
|
/*
|
||||||
|
* noop if we are not dumping anything about this table, or if we are
|
||||||
|
* doing a data-only dump
|
||||||
|
*/
|
||||||
|
if (!tbinfo->dobj.dump || dopt->dataOnly)
|
||||||
|
return;
|
||||||
|
|
||||||
if (tbinfo->relkind == RELKIND_SEQUENCE)
|
if (tbinfo->relkind == RELKIND_SEQUENCE)
|
||||||
dumpSequence(fout, tbinfo);
|
dumpSequence(fout, tbinfo);
|
||||||
else
|
else
|
||||||
|
Loading…
x
Reference in New Issue
Block a user