Search Results
https://dev.mysql.com/doc/internals/en/pstack-directory.html
In other words, the pstack files are not really part of the MySQL library. They are merely useful when you re-program some MYSQL code and it crashes. This is a set of publicly-available debugging aids which all do pretty well the same thing: display ...
https://dev.mysql.com/doc/internals/en/public-key-retrieval-example.html
set --default-authentication-plugin=sha256_password for the MySQL server: 46 00 00 00 0a 35 2e 36 2e 37 2d 6c 6f 67 00 04 F....5.6.7-log.. set --default-auth=sha256_password for the MySQL client, don't provide it with the servers public-key and ...
https://dev.mysql.com/doc/internals/en/replication.html
Status of this section: up to date 2009-10-21 This chapter describes MySQL replication principles, rules, and code, as it is supposed to work in version 5.1. The MySQL replication feature allows a server - the master - to send all changes to ...
https://dev.mysql.com/doc/internals/en/secure-password-authentication.html
The password is calculated by: SHA1( password ) XOR SHA1( "20-bytes random data from server" <concat> SHA1( SHA1( password ) ) ) .
https://dev.mysql.com/doc/internals/en/server-tools-directory.html
Quoting from the README file within this directory: "Instance Manager - manage MySQL instances locally and remotely. File description: mysqlmanager.cc - entry point to the manager, main, options.{h,cc} - handle startup options.
https://dev.mysql.com/doc/internals/en/source-file-archaeological-notes.html
log_event_old.h/log_event_old.cc (present in MySQL 5.1.18 and up): Classes to read and execute old versions of the row log events: Write_rows_log_event_old Update_rows_log_event_old Delete_rows_log_event_old Prior to MySQL 5.1.17, those classes ...
https://dev.mysql.com/doc/internals/en/stored-programs.html
The content formerly located in this chapter is now maintained in the Stored Programs section of the MySQL Server Doxygen documentation, available at https://dev.mysql.com/doc/index-other.html.
https://dev.mysql.com/doc/internals/en/support-for-update.html
If the table being updated contains timestamp columns, the updating of the timestamp will have to be managed in the update_row() call. Performing an update will depend on row format and storage implementation. Some storage engines will replace data ...
https://dev.mysql.com/doc/internals/en/transaction-overview.html
The storage engine stores transaction information in per-connection memory and also registers the transaction in the MySQL server to allow the server to later issue COMMIT and ROLLBACK operations. After work is completed, the MySQL server will call ... Transactions are not explicitly started on the storage engine level, but are instead implicitly started through calls to either start_stmt() or ...
https://dev.mysql.com/doc/internals/en/transactions-notes-on-ddl-and-normal-transaction.html
Besides, each DDL statement in MySQL begins with an implicit normal transaction commit (a call to end_active_trans()), and thus leaves nothing to modify. Perhaps, for consistency, MySQL should always commit a normal transaction after a DDL ... DDL ...