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 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/ab6eaee88420db58a948849d5a735997728d73a9 Modified Files -------------- doc/src/sgml/config.sgml | 4 +- src/backend/commands/analyze.c | 46 +++++++++++-- src/backend/commands/vacuum.c | 49 ++++++++++++-- .../isolation/expected/vacuum-concurrent-drop.out | 76 ++++++++++++++++++++++ src/test/isolation/isolation_schedule | 1 + .../isolation/specs/vacuum-concurrent-drop.spec | 45 +++++++++++++ 6 files changed, 208 insertions(+), 13 deletions(-)
