-
Notifications
You must be signed in to change notification settings - Fork 27
ps-10186-8.0 - [DOCS] - Document performance_schema.account_failed_lo… #572
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
patrickbirch
wants to merge
1
commit into
8.0
Choose a base branch
from
ps-10186-8.0
base: 8.0
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
# Misc. Performance Schema tables | ||
|
||
This page lists the `performance_schema` tables added to standard *MySQL* by *Percona Server for MySQL* that don't exist elsewhere in the documentation. | ||
|
||
## Performance schema tables | ||
|
||
### `performance_schema.account_failed_login_lock_status` | ||
|
||
The new `performance_schema.account_failed_login_lock_status` table is implemented in Percona Server for MySQL 8.0.44-35 and exposes information about temporary account locking from MySQL internal Access Control List (ACL) cache. | ||
|
||
This table is read-only, and global, per-database or per-table `SELECT` privilege on this table are required from users who want to access the table contents. | ||
|
||
| Column Name | Data Type | Description | | ||
|--------------------------|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------| | ||
| `USER` | `CHAR(..)` | Identifies the user account described by the table row | | ||
| `HOST` | `CHAR(..)` | Identifies the user account described by the table row | | ||
| `IS_TRACKING_ACTIVE` | `enum('YES','NO')` | Indicates whether failed login tracking is enabled for the account | | ||
| `MAX_ATTEMPTS` | `INTEGER` | Maximum number of failed login attempts allowed before account is locked (corresponds to FAILED_LOGIN_ATTEMPTS clause value in CREATE USER statement) | | ||
| `PASSWORD_LOCK_DAYS` | `INTEGER` | Number of days for which account will be temporarily locked after exceeding the MAX_ATTEMPS limit. Set to -1 if account is locked forever (corresponds to PASSWORD_LOCK_TIME clause value in CREATE USER) | | ||
| `IS_LOCKED` | `BOOLEAN` | Indicates if account is temporarily locked by failed login lock tracking. NULL if tracking is not enabled for account | | ||
| `REMAINING_ATTEMPTS` | `INTEGER` | Number of failed login attempts remaining before account will be locked. NULL if tracking is not enabled for account | | ||
| `REMAINING_DAYS_LOCKED` | `INTEGER` | Number of days for which account is locked due to failed login lock tracking. -1 means that account is locked "forever" (until server restart/FLUSH PRIVILEGES or specific account unlock). NULL if tracking is not enabled for account | |
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is worth emphasizing that the contents of this field has no relation to account locking not related to failed login attempt tracking. E.g. by adding something like: "Please note that if the account is locked using CREATE USER or ALTER TABLE statements with ACCOUNT LOCK clause, and not due to failed login lock tracking, this fact won't be reflected in this column. One should look at account_locked column in mysql.users table to see this instead".
What do you think?