Open
Conversation
AndreMouche
reviewed
Apr 15, 2020
| ``` | ||
|
|
||
| 从 DDL 记录可以看到，我们一共执行了 2 次 drop table t2 的操作，如果只执行 recover table t2 恢复的是最近一次删除的表。如果我希望恢复前面一次删除的动作，就需要用到下面的命令 | ||
| 从 DDL 记录可以看到，我们一共执行了 2 次 drop table t2 的操作，如果只执行 recover table t2，恢复的是最近一次删除的表。如果我希望恢复前面一次删除的动作，就需要用到下面的命令 |
Collaborator
There was a problem hiding this comment.
上面这个执行结果，如果在纸质版本或者 PDF 上肯能是个灾难。。要不然改成截图，或者 ADMIN SHOW DDL JOBS\G;?
zhexuany
reviewed
Apr 16, 2020
| ## 5.2 利用 Recover/Flashback 命令快速恢复误删表 | ||
|
|
||
| 对于 DBA 来说，删库跑路永远是被调侃的哏，近在眼前的某微商平台的大面积宕机事件给企业管理人员及数据库运维团队带来的启示仍在被不断讨论。当然为了应对大面积的恶意删库跑路行为，可能真的是防不胜防，不过这种情况也非常罕见。但是大家尤其是线上运维 DBA 在维护数据库的过程中，出现删错表/库的情况却是很容易出现的，下面来看一下 TiDB 提供的快速恢复误删表的功能。 | ||
| 对于 DBA 来说，删库跑路永远是被调侃的梗，近在眼前的某微商平台的大面积宕机事件给企业管理人员及数据库运维团队带来的启示仍在被不断讨论。当然为了应对大面积的恶意删库跑路行为，可能真的是防不胜防，不过这种情况也非常罕见。但是大家尤其是 DBA 在维护数据库的过程中，出现误删表/库的情况却是很容易出现的，下面来看一下 TiDB 提供的快速恢复误删表的功能。 |
There was a problem hiding this comment.
Suggested change
| 对于 DBA 来说，删库跑路永远是被调侃的梗，近在眼前的某微商平台的大面积宕机事件给企业管理人员及数据库运维团队带来的启示仍在被不断讨论。当然为了应对大面积的恶意删库跑路行为，可能真的是防不胜防，不过这种情况也非常罕见。但是大家尤其是 DBA 在维护数据库的过程中，出现误删表/库的情况却是很容易出现的，下面来看一下 TiDB 提供的快速恢复误删表的功能。 | |
| 对于 DBA 来说，删库跑路永远是被调侃的梗，近在眼前的某微商平台的大面积宕机事件给企业管理人员及数据库运维团队带来的启示仍在被不断讨论。当然为了应对大面积的恶意删库跑路行为，可能真的是防不胜防，不过这种情况也非常罕见。但是大家，尤其是 DBA 在维护数据库的过程中，出现误删表/库的情况却是很容易出现的，下面来看一下 TiDB 提供的快速恢复误删表的功能。 |
|
yubai seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
This PR is try to fix #721
How to contact you?