Tag Info

Hot answers tagged

2

Simple situations are recoverable with oncheck command. But your situation and this kind of corruption there is noway how recover the data from the "null" . For that you need recover your archive + logical log backups. Then you will recover all data to last status before the crash. Do you have ? hm.... I'm pretty sure your thinking now is : ooopsss... ...


2

If trigger evaluation fails for some reason, you should see an error message in "Configuration" -> "Triggers", on the right hand side: In this case, if you have just created "mysql.slowqueries" item and it does not yet have data older than half an hour, function "last(0,1800)" (which returns the last value half an hour ago) is going to fail. Once it has ...


1

Put simply, the password must be unencrypted in that particular configuration file because it needs to be read in order to authenticate to the database. However, it's possible to use no password by giving the proper permissions and appropriate hostname restrictions, but I do not recommend this as anyone with access to the server can use mysql to access the ...


1

I think you can check if your needed database working in simple manner in any shell $ mysql -uUSERNAME -pPASSWORD DATABASE -e exit and then check $? for exit code This command tries your specific credentials (USERNAME and PASSWORD) to connect to selected DATABASE and exit immediately. So, if connection is ok exitcode will be 0, and non-zero otherwise. ...


1

I think this is a good idea for less than 4 concurrent user using a Atom 2701 based NAS if you are using it as a test database server for less than 4 concurrent users. Atom is getting more and more popular in NAS. The dual core + HT architecture is capable to support 4 concurrent user. You may search for How Multi-Core Processors Accelerate your LAMP ...


1

From pgpool-II user manual max_pool*num_init_children <= (max_connections - superuser_reserved_connections) If you need 500 concurrent connections to pgpool then you need even more max_connections in your Postgres config. So for 500 concurrent connections you'd need: In pgpool.conf: num_init_children = 500 max_pool = 1 # there's no need for more if ...



Only top voted, non community-wiki answers of a minimum length are eligible