When VACUUM or ANALYZE skips a concurrently dropped table, log it

Enterprise / PostgreSQL - Robert Haas [postgresql.org] - 4 December 2017 20:25 EST

Hopefully, the additional logging will help avoid confusion that could otherwise result.

Nathan Bossart, reviewed by Michael Paquier, Fabrízio Mello, and me

ab6eaee884 When VACUUM or ANALYZE skips a concurrently dropped table, log it.
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(-)

Upstream: git.postgresql.org


  • Share