精华内容
下载资源
问答
  • mysql 查找配置文件 my.ini 位置方法

    万次阅读 多人点赞 2018-04-02 17:59:11
    见:https://blog.csdn.net/mayor125/article/details/54140454https://jingyan.baidu.com/article/7e4409531f75292fc0e2efe7.html个人备注:不显示文件类型时,my.ini 文件名就叫作 my, 文件属性才显示 ini。...

    前些天发现了一个巨牛的人工智能学习网站,通俗易懂,风趣幽默,忍不住分享一下给大家。点击跳转到教程。

    个人备注:不显示文件类型时,my.ini 文件名就叫作 my, 文件属性才显示 ini。

                     找到 my 文件看属性就知道是不是my.ini了

     

     

    问题描述:

    今天做个小实验需要修改MySQL的配置文件,我电脑上安装的是MySQL5.6,由于安装时间太久忘了安装在哪个目录下了,所以首先查了一下安装在本机上的MySQL的目录位置。

    在DOS命令行窗口登录MySQL,输入如下命令查看MySQL的安装目录和数据存放目录,MySQL的配置文件就在数据存放目录下:

     

     

    另外一种方法:

    在“开始 → 所有程序 → MySQL”下面找到MySQL的命令行客户端工具,右键选择该命令行工具查看“属性”,在“目标”里面也可以看到MySQL使用的配置文件位置。

    注意:ProgramData目录可能是“隐藏”的,如果在显示的分区中看不到的话就修改一下系统设置,让隐藏文件/文件夹可见。或者直接将ProgramData/MySQL/MySQL Server 5.6目录复制下来直接粘贴到文件夹的目录窗口中也可以。

    --------------------------------------------------- 我 是 分 隔 线 ----------------------------------------------------------

     

    第一步在我们的电脑上面找到mysql的安装路径,点击进去。

    第二步进去之后可以看到my.ini在mysql安装路径的根目录,这是其中一种情况。

     

    第三步另外一种情况是我们在mysql安装目录找不到,看到了my-default.ini文件,这时my.ini在“C:\ProgramData\MySQL\MySQL Server 5.6”目录下面,我们首先需要找到ProgramData文件夹,这是一个隐藏文件,需要隐藏文件可见才行,或者可以直接检索。

    第四步我们可以看到在“C:\ProgramData\MySQL\MySQL Server 5.6”目录下面找到了my.ini文件。

     

    展开全文
  • MySql 5.7 my.ini 位置(my.ini)在哪?

    万次阅读 热门讨论 2017-09-19 09:15:04
    my.ini windows10操作系统下: 1. 由于我们使用MySql 时,需要修改mysql 的 my.ini 的配置文件。 2. 但是 mysql 5.7 的 my.ini 位置并不在 C:\Program Files\MySQL\MySQL Server 5.7

    windows10操作系统下:

    1. 由于我们使用MySql 时,需要修改mysql 的 my.ini 的配置文件。


    2. 但是 mysql 5.7 的 my.ini 位置并不在 C:\Program Files\MySQL\MySQL Server 5.7

    此目录的my-default.ini 并不是我们要的:




    3. 如果安装在C盘的: 我们要进入 C:\ProgramData\MySQL\MySQL Server 5.7 此目录即可看到my.ini 此时你可以修改次配置啦!

    这里就是我们想要的啦:

    欢迎交流:不喜勿喷!!!





    展开全文
  • mysql配置文件my-default.ini my.ini修改后重启无效,原来是路径错了,记录一下: windows操作系统下: 1. 由于我们使用MySql 时,需要修改mysql 的 my.ini 的配置文件。 2. 但是 mysql 5.7 的 my.ini 位置并不...

    mysql配置文件my-default.ini  my.ini修改后重启无效,原来是路径错了,记录一下:

     

    windows操作系统下:

    1. 由于我们使用MySql 时,需要修改mysql 的 my.ini 的配置文件。

    2. 但是 mysql 5.7 的 my.ini 位置并不在 C:\Program Files\MySQL\MySQL Server 5.7 此目录的my-default.ini 并不是我们要的:

    3. 如果安装在C盘的: 我们要进入 C:\ProgramData\MySQL\MySQL Server 5.7 此目录即可看到my.ini 此时你可以修改次配置啦!
    ————————————————

     

    # MySql5.7配置文件my.ini设置
    [client]
    port = 3306
    socket = /tmp/mysql.sock
     
    [mysqld]
    ###############################基础设置#####################################
    #Mysql服务的唯一编号 每个mysql服务Id需唯一
    server-id = 1
     
    #服务端口号 默认3306
    port = 3306
     
    #mysql安装根目录
    basedir = /opt/mysql
     
    #mysql数据文件所在位置
    datadir = /opt/mysql/data
     
    #临时目录 比如load data infile会用到
    tmpdir  = /tmp
     
    #设置socke文件所在目录
    socket  = /tmp/mysql.sock
     
    #主要用于MyISAM存储引擎,如果多台服务器连接一个数据库则建议注释下面内容
    skip-external-locking
     
    #只能用IP地址检查客户端的登录,不用主机名
    skip_name_resolve = 1
    #数据库默认字符集,主流字符集支持一些特殊表情符号(特殊表情符占用4个字节)
    character-set-server = utf8mb4
     
    #数据库字符集对应一些排序等规则,注意要和character-set-server对应
    collation-server = utf8mb4_general_ci
     
    #设置client连接mysql时的字符集,防止乱码
    init_connect='SET NAMES utf8mb4'
     
    #是否对sql语句大小写敏感,1表示不敏感
    lower_case_table_names = 1
     
    #最大连接数
    max_connections = 400
    #最大错误连接数
    max_connect_errors = 1000
     
    #TIMESTAMP如果没有显示声明NOT NULL,允许NULL值
    explicit_defaults_for_timestamp = true
     
    #SQL数据包发送的大小,如果有BLOB对象建议修改成1G
    max_allowed_packet = 128M
     
    #MySQL连接闲置超过一定时间后(单位:秒)将会被强行关闭
    #MySQL默认的wait_timeout  值为8个小时, interactive_timeout参数需要同时配置才能生效
    interactive_timeout = 1800
    wait_timeout = 1800
     
    #内部内存临时表的最大值 ,设置成128M。
    #比如大数据量的group by ,order by时可能用到临时表,
    #超过了这个值将写入磁盘,系统IO压力增大
    tmp_table_size = 134217728
    max_heap_table_size = 134217728


     
    ##----------------------------用户进程分配到的内存设置BEGIN-----------------------------##
    ##每个session将会分配参数设置的内存大小
    #用于表的顺序扫描,读出的数据暂存于read_buffer_size中,当buff满时或读完,将数据返回上层调用者
    #一般在128kb ~ 256kb,用于MyISAM
    #read_buffer_size = 131072
    #用于表的随机读取,当按照一个非索引字段排序读取时会用到,
    #一般在128kb ~ 256kb,用于MyISAM
    #read_rnd_buffer_size = 262144
    #order by或group by时用到
    #建议先调整为2M,后期观察调整
    sort_buffer_size = 2097152
    #一般数据库中没什么大的事务,设成1~2M,默认32kb
    binlog_cache_size = 524288
     
    ############################日  志 设置##########################################
    #数据库错误日志文件
    log_error = error.log
     
    #慢查询sql日志设置
    slow_query_log = 1
    slow_query_log_file = slow.log
    #检查未使用到索引的sql
    log_queries_not_using_indexes = 1
    #针对log_queries_not_using_indexes开启后,记录慢sql的频次、每分钟记录的条数
    log_throttle_queries_not_using_indexes = 5
    #作为从库时生效,从库复制中如何有慢sql也将被记录
    log_slow_slave_statements = 1
    #慢查询执行的秒数,必须达到此值可被记录
    long_query_time = 2
    #检索的行数必须达到此值才可被记为慢查询
    min_examined_row_limit = 100
     
    #mysql binlog日志文件保存的过期时间,过期后自动删除
    expire_logs_days = 5
     
    ############################主从复制 设置########################################
    #开启mysql binlog功能
    log-bin=mysql-bin
    #binlog记录内容的方式,记录被操作的每一行
    binlog_format = ROW

    #作为从库时生效,想进行级联复制,则需要此参数
    log_slave_updates
     
    #作为从库时生效,中继日志relay-log可以自我修复
    relay_log_recovery = 1
     
    #作为从库时生效,主从复制时忽略的错误
    slave_skip_errors = ddl_exist_errors
     
    ##---redo log和binlog的关系设置BEGIN---##
    #(步骤1) prepare dml相关的SQL操作,然后将redo log buff中的缓存持久化到磁盘
    #(步骤2)如果前面prepare成功,那么再继续将事务日志持久化到binlog
    #(步骤3)如果前面成功,那么在redo log里面写上一个commit记录
    #当innodb_flush_log_at_trx_commit和sync_binlog都为1时是最安全的,
    #在mysqld服务崩溃或者服务器主机crash的情况下,binary log只有可能丢失最多一个语句或者一个事务。
    #但是都设置为1时会导致频繁的io操作,因此该模式也是最慢的一种方式。
    #当innodb_flush_log_at_trx_commit设置为0,mysqld进程的崩溃会导致上一秒钟所有事务数据的丢失。
    #当innodb_flush_log_at_trx_commit设置为2,只有在操作系统崩溃或者系统掉电的情况下,上一秒钟所有事务数据才可能丢失。
    #commit事务时,控制redo log buff持久化磁盘的模式 默认为1
    innodb_flush_log_at_trx_commit = 2
    #commit事务时,控制写入mysql binlog日志的模式 默认为 0
    #innodb_flush_log_at_trx_commit和sync_binlog都为1时,mysql最为安全但性能上压力也是最大
    sync_binlog = 1
    ##---redo log 和 binlog的关系设置END---##
     
    ############################Innodb设置##########################################
    #数据块的单位8k,默认是16k,16kCPU压力稍小,8k对select的吞吐量大
    #innodb_page_size的参数值也影响最大索引长度,8k比16k的最大索引长度小
    #innodb_page_size = 8192
    #一般设置物理存储的60% ~ 70%
    innodb_buffer_pool_size = 1G
     
    #5.7.6之后默认16M
    #innodb_log_buffer_size = 16777216
    #该参数针对unix、linux,window上直接注释该参数.默认值为NULL
    #O_DIRECT减少操作系统级别VFS的缓存和Innodb本身的buffer缓存之间的冲突
    innodb_flush_method = O_DIRECT
     
    #此格式支持压缩, 5.7.7之后为默认值
    innodb_file_format = Barracuda
     
    #CPU多核处理能力设置,假设CPU是2颗4核的,设置如下
    #读多,写少可以设成2:6的比例
    innodb_write_io_threads = 4
    innodb_read_io_threads = 4
     
    #提高刷新脏页数量和合并插入数量,改善磁盘I/O处理能力
    #默认值200(单位:页)
    #可根据磁盘近期的IOPS确定该值
    innodb_io_capacity = 500
     
    #为了获取被锁定的资源最大等待时间,默认50秒,超过该时间会报如下错误:
    # ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction
    innodb_lock_wait_timeout = 30
     
    #调整buffer pool中最近使用的页读取并dump的百分比,通过设置该参数可以减少转储的page数
    innodb_buffer_pool_dump_pct = 40
     
    #设置redoLog文件所在目录, redoLog记录事务具体操作内容
    innodb_log_group_home_dir = /opt/mysql/redolog/
     
    #设置undoLog文件所在目录, undoLog用于事务回滚操作
    innodb_undo_directory = /opt/mysql/undolog/
     
    #在innodb_log_group_home_dir中的redoLog文件数, redoLog文件内容是循环覆盖写入。
    innodb_log_files_in_group = 3
     
    #MySql5.7官方建议尽量设置的大些,可以接近innodb_buffer_pool_size的大小
    #之前设置该值较大时可能导致mysql宕机恢复时间过长,现在恢复已经加快很多了
    #该值减少脏数据刷新到磁盘的频次
    #最大值innodb_log_file_size * innodb_log_files_in_group <= 512GB,单文件<=256GB
    innodb_log_file_size = 1024M
     
    #设置undoLog文件所占空间可以回收
    #5.7之前的MySql的undoLog文件一直增大无法回收
    innodb_undo_log_truncate = 1
    innodb_undo_tablespaces = 3
    innodb_undo_logs = 128
     
    #5.7.7默认开启该参数 控制单列索引长度最大达到3072
    #innodb_large_prefix = 1
     
    #5.7.8默认为4个, Inodb后台清理工作的线程数
    #innodb_purge_threads = 4
     
    #通过设置配置参数innodb_thread_concurrency来限制并发线程的数量,
    #一旦执行线程的数量达到这个限制,额外的线程在被放置到对队列中之前,会睡眠数微秒,
    #可以通过设定参数innodb_thread_sleep_delay来配置睡眠时间
    #该值默认为0,在官方doc上,对于innodb_thread_concurrency的使用,也给出了一些建议:
    #(1)如果一个工作负载中,并发用户线程的数量小于64,建议设置innodb_thread_concurrency=0;
    #(2)如果工作负载一直较为严重甚至偶尔达到顶峰,建议先设置innodb_thread_concurrency=128,
    ###并通过不断的降低这个参数,96, 80, 64等等,直到发现能够提供最佳性能的线程数
    #innodb_thread_concurrency = 0
    ############################其他内容 设置##########################################
    [mysqldump]
    quick
    max_allowed_packet = 128M
    [mysql]
    no-auto-rehash
    [myisamchk]
    key_buffer_size = 20M
    sort_buffer_size = 256k
    read_buffer = 2M
    write_buffer = 2M
    [mysqlhotcopy]
    interactive-timeout
    [mysqld_safe]
    #增加每个进程的可打开文件数量.
    open-files-limit = 28192

    转载于:https://www.cnblogs.com/q149072205/p/11460566.html

    展开全文
  • 当初打开my.ini 修改内容保存时 因为权限原因没保存成功 也没看清提示 稀里糊涂的清空了my.ini 然后我就知道大事不好 打开mysql 果然我里面的数据库全没了 后来百度很多都没找到合适的方法 我先给赋予权限 让他可以...

    当初打开my.ini 修改内容保存时 因为权限原因没保存成功 也没看清提示 稀里糊涂的清空了my.ini
    然后我就知道大事不好 打开mysql 果然我里面的数据库全没了
    在这里插入图片描述
    后来百度很多都没找到合适的方法 我先给赋予权限 让他可以修改保存权限一直不能生效 但是重启之后权限生效了
    1、首先找到my.ini的位置
    在这里插入图片描述
    2、这里有很多类似一样的备份文件 打开复制到my.ini 我靠这个恢复的
    在这里插入图片描述
    重启电脑打开mysql 才成功
    在这里插入图片描述
    以管理员的方式打开cmd命令窗口(直接打开cmd运行,可能会报错),并且进入到mysql安装目录的bin目录下。然后输入命令mysqld install 显示成功

    2)再输入:mysqld –initialize 此时应该没有任何提示

    3)再输入:net start mysql 显示
    mysql -uroot -p

    # Other default tuning values
    # MySQL Server Instance Configuration File
    # ----------------------------------------------------------------------
    # Generated by the MySQL Server Instance Configuration Wizard
    # 
    # Installation Instructions
    # ----------------------------------------------------------------------
    # 
    # On Linux you can copy this file to /etc/my.cnf to set global options,
    # mysql-data-dir/my.cnf to set server-specific options
    # (@localstatedir@ for this installation) or to
    # ~/.my.cnf to set user-specific options.
    # 
    # On Windows you should keep this file in the installation directory 
    # of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To
    # make sure the server reads the config file use the startup option 
    # "--defaults-file". 
    # 
    # To run the server from the command line, execute this in a 
    # command line shell, e.g.
    # mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
    # 
    # To install the server as a Windows service manually, execute this in a 
    # command line shell, e.g.
    # mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
    # 
    # And then execute this in a command line shell to start the server, e.g.
    # net start MySQLXY
    # 
    # Guidelines for editing this file
    # ----------------------------------------------------------------------
    # 
    # In this file, you can use all long options that the program supports.
    # If you want to know the options a program supports, start the program
    # with the "--help" option.
    # 
    # More detailed information about the individual options can also be
    # found in the manual.
    # 
    # For advice on how to change settings please see
    # http://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html
    # 
    # 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]
    
    # pipe=
    
    # socket=MYSQL
    
    port=3306
    
    [mysql]
    no-beep=
    
    # default-character-set=
    
    # 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.=
    # 
    # server_type=3
    [mysqld]
    
    # The next three options are mutually exclusive to SERVER_PORT below.
    # skip-networking=
    # enable-named-pipe=
    # shared-memory=
    
    # shared-memory-base-name=MYSQL
    
    # The Pipe the MySQL Server will use
    # socket=MYSQL
    
    # 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="C:/Program Files/MySQL/MySQL Server 5.7/"
    
    # Path to the database root
    datadir=C:/ProgramData/MySQL/MySQL Server 5.7/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=
    
    # 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"
    
    # General and Slow logging.
    log-output=FILE
    
    general-log=0
    
    general_log_file="DESKTOP-ITPIA4D.log"
    
    slow-query-log=1
    
    slow_query_log_file="DESKTOP-ITPIA4D-slow.log"
    
    long_query_time=10
    
    # Binary Logging.
    # log-bin=
    
    # Error Logging.
    log-error="DESKTOP-ITPIA4D.err"
    
    # Server Id.
    server-id=1
    
    # Secure File Priv.
    secure-file-priv="C:/ProgramData/MySQL/MySQL Server 5.7/Uploads"
    
    # 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=151
    
    # 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_open_cache=2000
    
    # 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=44M
    
    # 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=10
    
    # *** 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=79M
    
    # 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=8M
    
    # 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
    
    # *** INNODB Specific options ***
    # innodb_data_home_dir=
    
    # 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=
    
    # 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=1M
    
    # 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=8M
    
    # 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=48M
    
    # 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=17
    
    # The increment size (in MB) for extending the size of an auto-extend InnoDB system tablespace file when it becomes full.
    innodb_autoextend_increment=64
    
    # The number of regions that the InnoDB buffer pool is divided into.
    # For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency,
    # by reducing contention as different threads read and write to cached pages.
    innodb_buffer_pool_instances=8
    
    # Determines the number of threads that can enter InnoDB concurrently.
    innodb_concurrency_tickets=5000
    
    # Specifies how long in milliseconds (ms) a block inserted into the old sublist must stay there after its first access before
    # it can be moved to the new sublist.
    innodb_old_blocks_time=1000
    
    # It specifies the maximum number of .ibd files that MySQL can keep open at one time. The minimum value is 10.
    innodb_open_files=300
    
    # When this variable is enabled, InnoDB updates statistics during metadata statements.
    innodb_stats_on_metadata=0
    
    # When innodb_file_per_table is enabled (the default in 5.6.6 and higher), InnoDB stores the data and indexes for each newly created table
    # in a separate .ibd file, rather than in the system tablespace.
    innodb_file_per_table=1
    
    # Use the following list of values: 0 for crc32, 1 for strict_crc32, 2 for innodb, 3 for strict_innodb, 4 for none, 5 for strict_none.
    innodb_checksum_algorithm=0
    
    # The number of outstanding connection requests MySQL can have.
    # This option is useful when the main MySQL thread gets many connection requests in a very short time.
    # It then takes some time (although very little) for the main thread to check the connection and start a new thread.
    # The back_log value indicates how many requests can be stacked during this short time before MySQL momentarily
    # stops answering new requests.
    # You need to increase this only if you expect a large number of connections in a short period of time.
    back_log=80
    
    # If this is set to a nonzero value, all tables are closed every flush_time seconds to free up resources and
    # synchronize unflushed data to disk.
    # This option is best used only on systems with minimal resources.
    flush_time=0
    
    # The minimum size of the buffer that is used for plain index scans, range index scans, and joins that do not use
    # indexes and thus perform full table scans.
    join_buffer_size=256K
    
    # The maximum size of one packet or any generated or intermediate string, or any parameter sent by the
    # mysql_stmt_send_long_data() C API function.
    max_allowed_packet=4M
    
    # If more than this many successive connection requests from a host are interrupted without a successful connection,
    # the server blocks that host from performing further connections.
    max_connect_errors=100
    
    # Changes the number of file descriptors available to mysqld.
    # You should try increasing the value of this option if mysqld gives you the error "Too many open files".
    open_files_limit=4161
    
    # If you see many sort_merge_passes per second in SHOW GLOBAL STATUS output, you can consider increasing the
    # sort_buffer_size value to speed up ORDER BY or GROUP BY operations that cannot be improved with query optimization
    # or improved indexing.
    sort_buffer_size=256K
    
    # The number of table definitions (from .frm files) that can be stored in the definition cache.
    # If you use a large number of tables, you can create a large table definition cache to speed up opening of tables.
    # The table definition cache takes less space and does not use file descriptors, unlike the normal table cache.
    # The minimum and default values are both 400.
    table_definition_cache=1400
    
    # Specify the maximum size of a row-based binary log event, in bytes.
    # Rows are grouped into events smaller than this size if possible. The value should be a multiple of 256.
    binlog_row_event_max_size=8K
    
    # If the value of this variable is greater than 0, a replication slave synchronizes its master.info file to disk.
    # (using fdatasync()) after every sync_master_info events.
    sync_master_info=10000
    
    # If the value of this variable is greater than 0, the MySQL server synchronizes its relay log to disk.
    # (using fdatasync()) after every sync_relay_log writes to the relay log.
    sync_relay_log=10000
    
    # If the value of this variable is greater than 0, a replication slave synchronizes its relay-log.info file to disk.
    # (using fdatasync()) after every sync_relay_log_info transactions.
    sync_relay_log_info=10000
    
    # Load mysql plugins at start."plugin_x ; plugin_y".
    plugin_load="mysqlx"
    
    # MySQL server's plugin configuration.
    # loose_mysqlx_port=33060
    
    # or MIXED. ROW is suggested for Group Replication.
    # Sets the binary logging format, and can be any one of STATEMENT, ROW,
    # ***** Group Replication Related *****
    # binlog_format=
    
    # NONE must be used with Group Replication.
    # and checking the event length (rather than a checksum) for each event.
    # that it is writing only complete events to the binary log by writing
    # The default is CRC32. When disabled (value NONE), the server verifies
    # binlog_checksum supports the values NONE (disabled) and CRC32.
    # Causes the master to write a checksum for each event in the binary log.
    # ***** Group Replication Related *****
    # binlog_checksum=
    
    # index file. Relay logs increase speed by using load-balancing between disks.
    # option, the value specified is also used as the base name for the relay log
    # sequence by adding a numeric suffix to the base name. If you specify this
    # The base name for the relay log. The server creates relay log files in
    # ***** Group Replication Related *****
    # relay_log=
    
    # register itself with the master.
    # on the master server. Leave the value unset if you do not want the slave to
    # during slave registration. This value appears in the output of SHOW SLAVE HOSTS
    # The host name or IP address of the slave to be reported to the master
    # ***** Group Replication Related *****
    # report_host=0.0
    
    # you have a special tunnel from the master or other clients to the slave.
    # slave registration. Set this only if the slave is listening on a nondefault port or if
    # The TCP/IP port number for connecting to the slave, to be reported to the master during
    # ***** Group Replication Related *****
    report_port=3306
    
    # used to identify transactions. ON must be used with Group Replication.
    # This option specifies whether global transaction identifiers (GTIDs) are
    # ***** Group Replication Related *****
    # gtid_mode=
    
    # option to ON before enabling GTID based replication.
    # only statements that can be safely logged using a GTID. You must set this
    # When enabled, the server enforces GTID consistency by allowing execution of
    # ***** Group Replication Related *****
    # enforce_gtid_consistency=
    
    # Group Replication.
    # the slave for this variable to have any effect. ON must be used with
    # logged to the slave's own binary log. Binary logging must be enabled on
    # Whether updates received by a slave server from a master server should be
    # ***** Group Replication Related *****
    # log_slave_updates=
    
    # The TABLE setting is required when multiple replication channels are configured.
    # to an InnoDB table in the mysql database, or to a file in the data directory.
    # Determines whether the slave server logs master status and connection information
    # ***** Group Replication Related *****
    # master_info_repository=
    
    # required when multiple replication channels are configured.
    # table in the mysql database, or to a file in the data directory. The TABLE setting is
    # Determines whether the slave server logs its position in the relay logs to an InnoDB
    # ***** Group Replication Related *****
    # relay_log_info_repository=
    
    # group members.
    # of extracting the writes from a transaction is required for conflict detection on all
    # are using Group Replication, this variable must be set to XXHASH64 because the process
    # Defines the algorithm used to hash the writes extracted during a transaction. If you
    # ***** Group Replication Related *****
    # transaction_write_set_extraction=
    
    # transaction_write_set_extraction=
    # group members.
    # of extracting the writes from a transaction is required for conflict detection on all
    # are using Group Replication, this variable must be set to XXHASH64 because the process
    # Defines the algorithm used to hash the writes extracted during a transaction. If you
    # ***** Group Replication Related *****
    lower_case_table_names=2
    
    
    展开全文
  • MySql 5.7 my.ini 位置(my.ini)在哪

    万次阅读 2018-06-08 11:39:33
    windows10操作系统下:...2. 但是 mysql 5.7 的 my.ini 位置并不在 C:\Program Files\MySQL\MySQL Server 5.7此目录的my-default.ini 并不是我们要的:3. 如果安装在C盘的: 我们要进入 C:\ProgramData\MySQL\MySQL ...
  • 安装MySQL配置文件 mysql8.0.13 my.ini设置文件 Windows下的配置文件直接可用
  • 我下载的是mysql5.7的安装包,安装包里没有my.ini,在网上找到对应的配置文件一下就是my.ini 的配置,其中红色部分替换成自己本地对应的路径。 # For advice on how to change settings please see # ...
  • 1,首先我按照了网上的打开隐藏文件,还是找不到my.ini(打开隐藏文件的方法: 2,如果1方法找到了。。就不用看2了。如果没找到就接受现实,需要自己创建my.ini然后重新配置。 (1)管理员运行cmd,前提是配置了...
  • 在C盘搜索 .ini文件,如果找到文件类型为配置设置的文件 复制到 Mysql文件夹下 修改文件名为 my.ini 完成
  • MySQL默认配置文件my.ini,但是安装完成后MySQL提供几个针对系统不同内存大小的配置文件分别为:my-huge.ini my-innode-heavy-4G.ini my-lage.ini my-medium.ini my-small.ini。 下面说一下如何修改使mysql可以引用...
  • 关于Mysql找不到配置文件my.ini或无法通过my.ini修改client配置的问题 最近开始上手学习Mysql,作为小白,遇到的问题多多,其中跟着教程尝试通过my.ini文件配置的时候发现不能通过my.ini修改[client]和[mysql]的配置...
  • 1. 复制my-default.ini文件一份,将复制后的文件名改成my.ini 2.在my.ini中[mysqld]标签下添加secure_file_priv = 3.如图
  • 今天我们今天主要向大家描述的是MySQL配置参数 my.ini/my.cnf,以下的文章就是对其实际操作的具体内容的详细解析
  • mysql中my.ini配置

    2017-09-12 10:25:02
    mysql中my.ini配置文件 my.ini配置
  • 1.没有my.ini的原因 mysql数据库的安装可以分为两种方式:解压方式 、安装方式。 两者的区别在于: 安装方式,通常会运行一个 向导程序,当按照向导,一步步完成安装,mysql会安装完成,并在安装目录下生成 一...
  • 本文针对mysql不同存储引擎,MyISAM与Innodb进行了讲解如何进行my.cnf(my.ini)的参数优化
  • my.ini.txt

    2019-10-25 13:45:55
    改资源为mysql5.7.25,windows版本,my.ini.txt配置文件
  • 备份:mysql5.6的my.inimy-default.ini # For advice on how to change settings please see # http://dev.mysql.com/doc/refman/5.6/en/server-configuration-defaults.html # *** DO NOT EDIT THIS FILE. It'...
  • ![我的my.ini](https://img-ask.csdn.net/upload/201512/06/1449384107_741677.jpg) 这是我的my.ini 网查了好多修改都弄不好~
  • MySQL中的my.ini.txt

    2021-01-22 21:25:17
    MySQL中的my.ini,由于修改其内容,会出现错误,现提供原版的ini文件供下载。
  • mysql所需的my.ini文件

    2020-03-29 19:53:52
    mysql-8.0.12-winx64数据库解压后 缺少my.ini文件需要新建,这里提供所需的my.ini文件。
  • 主要介绍了mysql服务性能优化—my.cnf_my.ini配置说明详解(16G内存),需要的朋友可以参考下
  • mysql my.ini

    热门讨论 2012-05-29 22:29:41
    mysql my.ini "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysql.exe" "--defaults-file=C:\Program Files\MySQL\MySQL Server 5.5\my.ini" "-uroot" "-p
  • mysql的my.ini范例配制文档,有中文解释,便于你设置my.ini配置
  • Mysql my.ini 配置文件详解
  • Windows上mysql8.0.17离线解压包带my.ini配置文件.rar...Windows上mysql8.0.17离线解压包带my.ini配置文件.rarWindows上mysql8.0.17离线解压包带my.ini配置文件.rarWindows上mysql8.0.17离线解压包带my.ini配置文件.rar
  • mysql配置文件 my.ini

    2020-04-22 17:17:25
    my.ini是MySQL数据库中使用的配置文件,修改这个文件可以达到更新配置的目的。修改my.ini文件后需要重启数据库

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 127,421
精华内容 50,968
关键字:

my.ini