Skip to content

Commit 689f9a0

Browse files
committed
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.
1 parent 8b99ede commit 689f9a0

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

src/bin/pg_dump/pg_dump.c

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14846,6 +14846,13 @@ dumpTable(Archive *fout, TableInfo *tbinfo)
1484614846
DumpOptions *dopt = fout->dopt;
1484714847
char *namecopy;
1484814848

14849+
/*
14850+
* noop if we are not dumping anything about this table, or if we are
14851+
* doing a data-only dump
14852+
*/
14853+
if (!tbinfo->dobj.dump || dopt->dataOnly)
14854+
return;
14855+
1484914856
if (tbinfo->relkind == RELKIND_SEQUENCE)
1485014857
dumpSequence(fout, tbinfo);
1485114858
else

0 commit comments

Comments
 (0)