Pam Astor wrote:
The ANSI-SQL syntax is to just use GRANT to create users. You will
still need to use GRANT twice for both users: joe@'%' and joe@'localhost'.
But I find the MySql syntax for creating user with CREATE USER and then
GRANT easier to follow:
CREATE USER joe@'%' IDENTIFIED BY
Eric Bergen schrieb:
Hi Jan,
You have two separate issues here. First the issue with the link
between the external slave and the master. Running mysql through
something like stunnel may help with the connection and data loss
issues.
I wonder how any corruption could happen on a TCP
New queries, tuning the insert (DELAYED) we make on the database. The
clients have not to wait to the io response of the thread of the
database that inserts the data and the repl data.
-Mensaje original-
De: Tim McDaniel [mailto:[EMAIL PROTECTED]
Enviado el: viernes 18 de abril de 2008
Hi,
I am using myisam engine and there is 25 GB of data. The data is keep on
growing. How should i know that when to increase the key_buffer_size.
currently it is 2G.
Thanks
--
Krishna Chandra Prajapati
MySQL DBA,
Ed Ventures e-Learning Pvt.Ltd.
1-8-303/48/15, Sindhi Colony
P.G.Road,
Hi,
Keep your key_buffer_size to 25% of your physical RAM.
This should be good.
regards
anandkl
On 4/21/08, Krishna Chandra Prajapati [EMAIL PROTECTED] wrote:
Hi,
I am using myisam engine and there is 25 GB of data. The data is keep on
growing. How should i know that when to increase
Is there any way to prevent UPDATEs on one database on one mysql
instance from affecting SELECTs on other databases in the same
instance? I'm noticing a whole bunch of backed up connections on
other databases when I run massive UPDATEs on one.
Thanks!
--
MySQL General Mailing List
For list
Dear List,
I have installed a binary package mysql-5.0.51a-osx10.5-x86_64.dmg
I can start up/shutdown MySQL and connect to MySQL server, but I cant
change a root password as required.
---begin example---
e7253:~ olichka$ cd /usr/local/mysql
e7253:mysql olichka$ sudo ./bin/mysqld_safe
The ANSI-SQL syntax is to just use GRANT to create users. You will
still need to use GRANT twice for both users: joe@'%' and joe@'localhost'.
But I find the MySql syntax for creating user with CREATE USER and then
GRANT easier to follow:
CREATE USER joe@'%' IDENTIFIED BY
Olga Lyashevska wrote:
e7253:mysql olichka$ /usr/local/mysql/bin/mysql
Try:
$ /usr/local/mysql/bin/mysql -u root -p
It looks like you aren't logging into MySQL as root, so you don't have
permission to set the root password. (If you don't give -u, it uses
your OS X short user name
TCP checksums aren't as strong as encryption. It's rare but corruption
can happen.
Where are you reading the positions from and how are you taking the
snapshot to restore the slave?
On Mon, Apr 21, 2008 at 12:30 AM, Jan Kirchhoff [EMAIL PROTECTED] wrote:
Eric Bergen schrieb:
Hi Jan,
Dear List,
I have solved my problem I think.
For some reasons 'alias mysql=/usr/local/mysql/bin/mysql' didnt work for me.
When I type '/usr/local/mysql/bin/mysql -u root' I can log in as a root
and change password.
Later I can log in: '/usr/local/mysql/bin/mysql -u root -p'
Thank you,
Olga
Victor,
Please give us an example with the python removed and include the
actual syntax error.
-Eric
On Fri, Apr 18, 2008 at 8:41 AM, Victor Subervi [EMAIL PROTECTED] wrote:
Hi;
The python code works properly, so I assume this is a strictly MySQL
question now :)
If I grab an image in
I have a MySQL 5.x box and I am thinking about moving it to another more
powerful server. I would be able to schedule some downtime so that's not an
issue. How complicated a process would this be? I don't want to upgrade the
software or anything, just move the existing tables, users and
A simple rsync should do the trick. How long will depend on how much
data you have. I would just shut down the server, copy over the data
directory and start the new server up. Should be a piece of cake.
Keith
David Ruggles wrote:
I have a MySQL 5.x box and I am thinking about moving it
hi list,
reading manual on mysql regarding auto_increment with multiple-column
index:
CREATE TABLE animals (
grp ENUM('fish','mammal','bird') NOT NULL,
id MEDIUMINT NOT NULL AUTO_INCREMENT,
name CHAR(30) NOT NULL,
PRIMARY KEY (grp,id)
);
INSERT INTO animals (grp,name) VALUES
On Mon, April 21, 2008 07:28, Waynn Lue wrote:
Is there any way to prevent UPDATEs on one database on one mysql
instance from affecting SELECTs on other databases in the same
instance? I'm noticing a whole bunch of backed up connections on
other databases when I run massive UPDATEs on one.
16 matches
Mail list logo