When VACUUM or ANALYZE skips a concurrently dropped table, log it.
Hopefully, the additional logging will help avoid confusion that could otherwise result. Nathan Bossart, reviewed by Michael Paquier, Fabrízio Mello, and me
Showing
- doc/src/sgml/config.sgml 2 additions, 2 deletionsdoc/src/sgml/config.sgml
- src/backend/commands/analyze.c 41 additions, 5 deletionssrc/backend/commands/analyze.c
- src/backend/commands/vacuum.c 43 additions, 6 deletionssrc/backend/commands/vacuum.c
- src/test/isolation/expected/vacuum-concurrent-drop.out 76 additions, 0 deletionssrc/test/isolation/expected/vacuum-concurrent-drop.out
- src/test/isolation/isolation_schedule 1 addition, 0 deletionssrc/test/isolation/isolation_schedule
- src/test/isolation/specs/vacuum-concurrent-drop.spec 45 additions, 0 deletionssrc/test/isolation/specs/vacuum-concurrent-drop.spec
Loading
Please register or sign in to comment