NotificationsYou must be signed in to change notification settings
Fork5
Star26

Commit689f9a0

committed

In dumpTable, re-instate the skipping logic

Pretty sure I removed this based on some incorrect thinking that it wasno longer possible to reach this point for a table which will not bedumped, but that's clearly wrong.Pointed out on IRC by Erik Rijkers.

1 parent8b99ede commit689f9a0Copy full SHA for 689f9a0

File tree

1 file changed

-0

lines changed

src/bin/pg_dump
- pg_dump.c

1 file changed

-0

lines changed

`‎src/bin/pg_dump/pg_dump.c`

Lines changed: 7 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -14846,6 +14846,13 @@ dumpTable(Archive fout, TableInfo tbinfo)`
`14846`	`14846`	`DumpOptions *dopt = fout->dopt;`
`14847`	`14847`	`char *namecopy;`
`14848`	`14848`
	`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`	`+`
`14849`	`14856`	`if (tbinfo->relkind == RELKIND_SEQUENCE)`
`14850`	`14857`	`dumpSequence(fout, tbinfo);`
`14851`	`14858`	`else`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit689f9a0

File tree

1 file changed

1 file changed

`‎src/bin/pg_dump/pg_dump.c`

0 commit comments