NotificationsYou must be signed in to change notification settings
Fork6
Star31

Commitf4428cc

committed

Ignore invalid indexes in pg_dump.

Dumping invalid indexes can cause problems at restore time, for exampleif the reason the index creation failed was because it tried to enforcea uniqueness condition not satisfied by the table's data. Also, if theindex creation is in fact still in progress, it seems reasonable toconsider it to be an uncommitted DDL change, which pg_dump wouldn't beexpected to dump anyway.Back-patch to all active versions, and teach them to ignore invalidindexes in servers back to 8.2, where the concept was introduced.Michael Paquier

1 parent40ce24c commitf4428ccCopy full SHA for f4428cc

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: 2 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -4028,6 +4028,7 @@ getIndexes(TableInfo tblinfo[], int numTables)`
`4028`	`4028`	`"i.indexrelid = c.conindid AND "`
`4029`	`4029`	`"c.contype IN ('p','u','x')) "`
`4030`	`4030`	`"WHERE i.indrelid = '%u'::pg_catalog.oid "`
	`4031`	`+"AND i.indisvalid "`
`4031`	`4032`	`"ORDER BY indexname",`
`4032`	`4033`	`tbinfo->dobj.catId.oid);`
`4033`	`4034`	`}`
`@@ -4056,6 +4057,7 @@ getIndexes(TableInfo tblinfo[], int numTables)`
`4056`	`4057`	`"ON (d.refclassid = c.tableoid "`
`4057`	`4058`	`"AND d.refobjid = c.oid) "`
`4058`	`4059`	`"WHERE i.indrelid = '%u'::pg_catalog.oid "`
	`4060`	`+"AND i.indisvalid "`
`4059`	`4061`	`"ORDER BY indexname",`
`4060`	`4062`	`tbinfo->dobj.catId.oid);`
`4061`	`4063`	`}`

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!

Commitf4428cc

File tree

1 file changed

1 file changed

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

0 commit comments