Teach gpcheckcat to drop temp toast schemas along with temp schemas.
And allow DROP SCHEMA on temp toast schemas, like we allow dropping temp schemas. These are fixups for commit 2619b329, in reaction to a test failure in the "gpcheckcat should drop leaked schemas" scenario in MU_gpcheckcat test suite. The test opens a session, creates a temp table in it, and then kills the server. That leaks the temp schema in the QD node, because the backend dies abruptly, but the QE backends exit cleanly when the QD-QE connection is lost, and they do remove the temp schema. That creates an inconsistency between the QD and QE nodes. gpcheckcat knows about that problem, and removes any orhpaned temp schemas; that's what the test tests. However, gpcheckcat didn't know about temp toast schemas. Until commit 2619b329, the temp toast schemas were always leaked, whether the backend exited cleanly or not, so there was no inconsistency between the QD and QE nodes. After that commit, the temp toast schema behaves the same as the temp schema, and the test started failing. The fix is straightforward: teach gpcheckcat to clean up temp toast schemas, just like it cleans up temp schemas. Backpatch to 5X_STABLE, like commit 2619b329.
Showing
想要评论请 注册 或 登录