Skip to content

Allow VACUUM to run again for a table on --resume - #70

Open
teknogeek0 wants to merge 1 commit into
mainfrom
fix/resume-vacuum-summary
Open

teknogeek0 wants to merge 1 commit into
mainfrom
fix/resume-vacuum-summary

Conversation

@teknogeek0

Copy link
Copy Markdown
Collaborator

A resume after a failed index phase sends tables that the earlier run already vacuumed to VACUUM again. The plain insert into vacuum_summary broke its unique(tableoid) constraint ([SQLite 19] constraint failed) and failed the resume. This change uses insert or replace.

The new resume-vacuum suite makes one CREATE INDEX fail on the first clone, then runs clone --resume. It fails without the fix and passes with it.

Tests: full PG18 suite, 36 of 36 suites pass.

A resume after a failed index phase sends tables that the earlier run
already vacuumed to VACUUM again. The plain insert into vacuum_summary
broke its unique(tableoid) constraint and failed the resume. Use insert
or replace, and add the resume-vacuum test suite.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant