New answers tagged

0

max_connections and ulimit and SSDs have virtually no relationship to each other. ulimit is an upper bound (unnecessarily low at 1024) on the number of files that can be open in any 'process'. (mysqld is a 'process'.) It does relate to table_open_cache, which is now set dynamically based on ulimit. (In older versions, it was not automatically set.) ...


0

If the SSD you are talking is "Solid State Drive", it will only act as an ordinary drive with faster read and write. That is the reason why servers are being migrated to SSD drives for critical parts of it. Increasing the max_connection will also increase CPU and Memory Usage. I won't recommend a limit of 3000. About the issue with kernel limit of open ...


-1

Solution for PostgreSQL: We can avoid using rules - Stop slave daemons - Create ON DELETE and ON UPDATE DO INSTEAD NOTHING CREATE RULE void_delete AS ON DELETE TO reptest DO INSTEAD NOTHING - rule Apply RULE on table ALTER TABLE reptest ENABLE REPLICA RULE void_delete; Now, you can notice below that DELETE has no impact on Slave Node ...


0

I will recommend to move from php-mysql to php-mysqlnd (which provides the same set of extensions: mysql, mysqli and pdo_mysql), and thus, get rid of dependency on libmysqlclient: # yum shell --enablerepo=remi > remove php-mysql > install php-mysqlnd > run Notice: PHP 5.4 is now EOL, I also recommend to upgrade to 5.5 or 5.6. And 5.4 is also the ...


1

[!!] Total fragmented tables: 551 -- bogus, ignore it [0.071 qps], -- very lightly loaded [!!] Maximum possible memory usage: 126.3G (100% of installed RAM) -- bogus, ignore it [OK] Highest usage of available connections: 0% (2/600) -- consider lowering max_connections [OK] Key buffer size / total MyISAM indexes: 1.0G/153.6M -- lower key_buffer_size ...


0

Not really. Instead, you could do something like SELECT CONCAT("UPDATE ", table_schema, ".", table_name, " SET foo = replace(foo, 'this', 'that');") FROM information_schema.tables WHERE ... to generate the desired 50+ UPDATE statements. Then copy and paste them into the mysql commandline tool. (Or you could construct a shell ...


0

In my insane research for a solution I took a look to /var/log/mysqld.log and found this line: [Note] A temporary password is generated for root@localhost: abc123 Looks like mysql 5.7+ generates a random password in the installation and prompted in that file.


0

When running this command mysqlbinlog --verbose --base64-output=decode-rows mysql-bin.000004 | tail -n 5 | head -n 1 it gives an error. After investigation we found that last week there was power failure, because of which replication isn't happening. So the workaround is to take a new backup of master and restore the replication.


0

I tried to solve this in many ways but, didn't got any workaround. then I tried to redo the whole thing again with the below steps. I took backup of mysql user from Master Host mysqldump -u root -p mysql user > user_table_dump.sql and Restored in on slave mysql -u root -p mysql < user_table_dump.sql At the time of restored the master dump on ...


0

The error itself is happening because there is a create view (or procedure) statement and the slave doesn't have the user who created it. In mysqldump you will have this format: CREATE ALGORITHM=UNDEFINED DEFINER=`lipl_ga_app`@`%` SQL SECURITY DEFINER... That's not specific to replication. It happens even if you would want to restore it to an empty db. ...


1

You try to connect with / as sysdba, which normally connects locally, and you still get errors related to TNS and listener. Actually, there is a not well-known environment variable, called TWO_TASK, and if you set that, SQL*Plus will automatically try to connect using the value of the variable as a TNS entry. So if you use TWO_TASK, instead of this: ...


0

something is very "off" in that terminal session. You are not connecting with a net description, so you shouldn't even be hitting the listener at all. I cannot reproduce that error with that syntax. In any event, your syntax really should be sqlplus / as sysdba with a space between the slash and the 'as', and no quote marks.


0

I just came across a way to find out which databases the old PG_DATA directory contained. It's a bit hackish, and too late for me, but it might be useful for somebody else in the future. Information about database names (etc) is not stored in PG_DATA/base, but rather in PG_DATA/global. The files in that directory are (in my case, at least) small enough to ...


1

The postgres user by default has no password. To remove a user password (in this case for the postgres user/role): alter role postgres password null;



Top 50 recent answers are included