View mysql log

View mysql query log

MySQL logging operations:

  1. Confirm whether logging is enabled

    After landing mysql, execute sql statement:show variables like 'log_bin';

    mysql> show variables like 'log_bin';
    +---------------+-------+
    | Variable_name | Value |
    +---------------+-------+
    | log_bin       | OFF   |
    +---------------+-------+
    1 row in set (0.00 sec)            

    Is not currently logging is enabled. If Value is ON, the enabled logging. Log file in the data directory of mysql installation directory.
    View the current log:mysql> show master status;

  2. Query Log: log

    Open the way: In the [mysqld] option my.ini, and add the code:
    log=C:/backend/MySQL/MySQL Server 5.5/log.txt

  3. Error Log: log-error

    Open the way: In the [mysqld] option my.ini, and add the code:
    log-error=C:/backend/MySQL/MySQL Server 5.5/log-error.txt

  4. Binary log: log-bin

    Open the way: In the [mysqld] option my.ini, and add the code:
    log-bin=C:/backend/MySQL/MySQL Server 5.5/log-bin

  5. Restart mysql service

    Run as Administrator cmd , enter:

    C:\Windows\system32>net stop mysql
    The MySQL service is stopping.
    The MySQL service was stopped successfully.
    
    C:\Windows\system32>net start mysql
    The MySQL service is starting.
    The MySQL service was started successfully.

MySQL configuration file: my.ini

  1. my.ini role

    my.ini MySQL database is used in the configuration file, this file can be modified to achieve the purpose of updating the configuration.

  2. Find the location of the my.ini

    my.ini stored in the root directory MySql installation.

If you forget the installation directory, you can view the installation directory by sql statement. mysql> select @@ basedir;

  1. my.ini specific content description:

    # CLIENT SECTION
    # ----------------------------------------------------------------------
    #
    # The following options will be read by MySQL client applications.
    # Note that only client applications shipped by MySQL are guaranteed
    # to read this section. If you want your own MySQL client program to
    # honor these values, you need to specify it as an option during the
    # MySQL client library initialization.
    #
    [client]
    
    port=3306
    
    [mysql]
    
    default-character-set=gb2312

    Shown above is the client's parameter, [Client] and [MySQL] is the client, the following profile parameters are:

      1.port parameter indicates the port MySQL database, the default port is 3306, if you need to change the port number, then it can be modified here.

      2.default-character-set argument is the client's default character set, if you want it to support Chinese, or can be set to gbk utf8.

      3. There is also a password parameter, where the value of the password set parameters when you can not enter directly into the login password

    # SERVER SECTION
    # ----------------------------------------------------------------------
    #
    # The following options will be read by the MySQL Server. Make sure that
    # you have installed the server correctly (see above) so it reads this 
    # file.
    #
    [mysqld]
    
    # The TCP/IP Port the MySQL Server will listen on
    port=3306
    
    
    #Path to installation directory. All paths are usually resolved relative to this.
    basedir="E:/Java/Mysql/"
    
    #Path to the database root
    datadir="C:/ProgramData/MySQL/MySQL Server 5.5/Data/"
    
    # The default character set that will be used when a new schema or table is
    # created and no character set is defined
    character-set-server=gb2312
    
    # The default storage engine that will be used when create new tables when
    default-storage-engine=INNODB
    
    # Set the SQL mode to strict
    sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
    
    # The maximum amount of concurrent sessions the MySQL server will
    # allow. One of these connections will be reserved for a user with
    # SUPER privileges to allow the administrator to login even if the
    # connection limit has been reached.
    max_connections=100
    
    # Query cache is used to cache SELECT results and later return them
    # without actual executing the same query once again. Having the query
    # cache enabled may result in significant speed improvements, if your
    # have a lot of identical queries and rarely changing tables. See the
    # "Qcache_lowmem_prunes" status variable to check if the current value
    # is high enough for your load.
    # Note: In case your tables change very often or if your queries are
    # textually different every time, the query cache may result in a
    # slowdown instead of a performance improvement.
    query_cache_size=0
    
    # The number of open tables for all threads. Increasing this value
    # increases the number of file descriptors that mysqld requires.
    # Therefore you have to make sure to set the amount of open files
    # allowed to at least 4096 in the variable "open-files-limit" in
    # section [mysqld_safe]
    table_cache=256
    
    # Maximum size for internal (in-memory) temporary tables. If a table
    # grows larger than this value, it is automatically converted to disk
    # based table This limitation is for a single table. There can be many
    # of them.
    tmp_table_size=35M
    
    
    # How many threads we should keep in a cache for reuse. When a client
    # disconnects, the client's threads are put in the cache if there aren't
    # more than thread_cache_size threads from before.  This greatly reduces
    # the amount of thread creations needed if you have a lot of new
    # connections. (Normally this doesn't give a notable performance
    # improvement if you have a good thread implementation.)
    thread_cache_size=8
    
    #*** MyISAM Specific options
    
    # The maximum size of the temporary file MySQL is allowed to use while
    # recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
    # If the file-size would be bigger than this, the index will be created
    # through the key cache (which is slower).
    myisam_max_sort_file_size=100G
    
    # If the temporary file used for fast index creation would be bigger
    # than using the key cache by the amount specified here, then prefer the
    # key cache method.  This is mainly used to force long character keys in
    # large tables to use the slower key cache method to create the index.
    myisam_sort_buffer_size=69M
    
    # Size of the Key Buffer, used to cache index blocks for MyISAM tables.
    # Do not set it larger than 30% of your available memory, as some memory
    # is also required by the OS to cache rows. Even if you're not using
    # MyISAM tables, you should still set it to 8-64M as it will also be
    # used for internal temporary disk tables.
    key_buffer_size=55M
    
    # Size of the buffer used for doing full table scans of MyISAM tables.
    # Allocated per thread, if a full scan is needed.
    read_buffer_size=64K
    read_rnd_buffer_size=256K
    
    # This buffer is allocated when MySQL needs to rebuild the index in
    # REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
    # into an empty table. It is allocated per thread so be careful with
    # large settings.
    sort_buffer_size=256K

    The above is the server off parameters, it is an introduction parameters:

      1.port parameter is the port of the database.

      2.basedir parameter represents the installation path of MySQL.

      3.datadir parameter represents the MySQL data file storage location is the storage location of the database table.

      4.default-character-set parameter indicates the default character set, this character set is the server side.

      5.default-storage-engine parameter default storage engine.

      6.sql-mode parameter indicates parameters SQL mode, you can set stringent test SQL statements by this parameter.

      7.max_connections parameter indicates the maximum number of simultaneous connections to access the MySQL server, one connection is reserved, leaving the administrators.

      8.query_cache_size parameter indicates the time of the query cache size, the cache can store information previously queried by the select statement, you can come up with information directly from the cache when the query again.

      9.table_cache parameter indicates the total number of open tables for all processes.

      10.tmp_table_size parameter indicates the amount of memory in a temporary table.

      11.thread_cache_size parameters expressed reservations cache client thread.

      12.myisam_max_sort_file_size parameter indicates the maximum size of the temporary file MySQL is allowed to rebuild the index.

      13.myisam_sort_buffer_size parameter indicates the cache size when rebuilding the index.

      14.key_buffer_size parameter indicates keyword cache size.

      15.read_buffer_size parameter indicates the cache size MyISAM table full table scan.

      16.read_rnd_buffer_size parameter indicates the sorted data into the cache.

      17.sort_buffer_size parameter indicates the size of the buffer for sorting

    #*** INNODB Specific options ***
    
    
    # Use this option if you have a MySQL server with InnoDB support enabled
    # but you do not plan to use it. This will save memory and disk space
    # and speed up some things.
    #skip-innodb
    
    # Additional memory pool that is used by InnoDB to store metadata
    # information.  If InnoDB requires more memory for this purpose it will
    # start to allocate it from the OS.  As this is fast enough on most
    # recent operating systems, you normally do not need to change this
    # value. SHOW INNODB STATUS will display the current amount used.
    innodb_additional_mem_pool_size=3M
    
    # If set to 1, InnoDB will flush (fsync) the transaction logs to the
    # disk at each commit, which offers full ACID behavior. If you are
    # willing to compromise this safety, and you are running small
    # transactions, you may set this to 0 or 2 to reduce disk I/O to the
    # logs. Value 0 means that the log is only written to the log file and
    # the log file flushed to disk approximately once per second. Value 2
    # means the log is written to the log file at each commit, but the log
    # file is only flushed to disk approximately once per second.
    innodb_flush_log_at_trx_commit=1
    
    # The size of the buffer InnoDB uses for buffering log data. As soon as
    # it is full, InnoDB will have to flush it to disk. As it is flushed
    # once per second anyway, it does not make sense to have it very large
    # (even with long transactions).
    innodb_log_buffer_size=2M
    
    # InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
    # row data. The bigger you set this the less disk I/O is needed to
    # access data in tables. On a dedicated database server you may set this
    # parameter up to 80% of the machine physical memory size. Do not set it
    # too large, though, because competition of the physical memory may
    # cause paging in the operating system.  Note that on 32bit systems you
    # might be limited to 2-3.5G of user level memory per process, so do not
    # set it too high.
    innodb_buffer_pool_size=107M
    
    # Size of each log file in a log group. You should set the combined size
    # of log files to about 25%-100% of your buffer pool size to avoid
    # unneeded buffer pool flush activity on log file overwrite. However,
    # note that a larger logfile size will increase the time needed for the
    # recovery process.
    innodb_log_file_size=54M
    
    # Number of threads allowed inside the InnoDB kernel. The optimal value
    # depends highly on the application, hardware as well as the OS
    # scheduler properties. A too high value may lead to thread thrashing.
    innodb_thread_concurrency=18

    The above is a parameter used by the InnoDB storage engine, it is an introduction parameters:

      1.innodb_additional_mem_pool_size additional parameter indicates the memory pool, to the content storage InnoDB tables.

      2.innodb_flush_log_at_trx_commit parameter is to set the timing of submission of the log, if set to 1, InnoDB will each commit after the transaction log is written to disk.

      3.innodb_log_buffer_size parameter indicates the size of the buffer for storing log data.

      4.innodb_buffer_pool_size parameter indicates the size of the cache, InnoDB using a buffer pool index and save the original data.

      5.innodb_log_file_size parameter indicates the size of the log file.

      6.innodb_thread_concurrency parameter represents the InnoDB storage engine allows a maximum number of threads.

Note: After each modify parameters, you must restart the MySQL service will be effective.

Reproduced in: https: //www.cnblogs.com/xiaohaifengke/p/11043633.html

Guess you like

Origin blog.csdn.net/weixin_34335458/article/details/93655817