pgsql: When VACUUM or ANALYZE skips a concurrently dropped table, log i

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: When VACUUM or ANALYZE skips a concurrently dropped table, log i
Date: 2017-12-04 20:26:08
Message-ID: E1eLxJZ-0002HB-02@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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(-)

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2017-12-04 22:03:24 pgsql: Clean up assorted messiness around AllocateDir() usage.
Previous Message Andres Freund 2017-12-04 20:21:42 Re: pgsql: Add some regression tests that exercise hash join code.

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-12-04 20:27:16 Re: [HACKERS] Additional logging for VACUUM and ANALYZE
Previous Message Tom Lane 2017-12-04 20:15:08 Is it OK to ignore directory open failure in ResetUnloggedRelations?