Hi, Joerg
Thanks you very much.
I slove it with second method(hack "sql/share/Makefile"
http://lists.mysql.com/commits/102846).
r...@localhost:(none) 09:09:30>select version();
+
What Shawn said is important.
Better options:
1. Use InnoDB, and then you can make a consistent backup with `mysqldump
--single-transaction > backup.sql` and keep your db server actively responding
to requests at the same time.
2. Use something like LVM to create filesytem snapshots which allo
Mitchell Maltenfort wrote:
I'm using MySQL to manage data on my computer .
The total data is 50 Gig in MyISAM folders.
As I type, I already have the folder with the myd, frm, etc being
copied offsite. As I understand it, if this computer dies tomorrow, I
can reinstall MySQL on a new computer,
I'm using MySQL to manage data on my computer .
The total data is 50 Gig in MyISAM folders.
As I type, I already have the folder with the myd, frm, etc being
copied offsite. As I understand it, if this computer dies tomorrow, I
can reinstall MySQL on a new computer, drag over the archive, stick
On this level, it's more of an apache/web-server-in-general issue.
There are 2 connections to be considered here: the connection between
the browser and the web server and the connection between the
webserver (running PHP for example) and the database and they have
very different behaviours.
If t
Hi Yang Wang, everybody!
Yang Wang wrote:
> Dear All,
>
> I hit belown problem when i compile(make install) 5.5.4-M3 on centos 5.0.
>
>
>
> -bash-3.1# cat /etc/redhat-releas
On Fri, Apr 16, 2010 at 1:31 PM, Nigel Wood wrote:
> P.S. Sorry to the other list users for a PHP oriented discussion.
>
Get a room, you two :-)
--
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel
> > Consider the following concept,
> >
> > ~/index.php
> >
> > #1. Fetch data from an external webpage using PHP Curl;
> > #2. Preg_match/Prepare Data to INSERT from local MySQL; - this may take a
> > few secs
> > #3. While Loop { INSERT data (from #2) into local MySQL } - this may take
> > only m
How recent is your source tree? It looks like it may be a recent issue, so
going back 6 months or so
might solve it.
The bug report you noted doesn't seem to have a work-around, though I would
guess you could look at
the source and probably fix the issue quite easily. It looks like you have do
On Mon, Apr 19, 2010 at 12:16 PM, Rob Wultsch wrote:
> One way or another this
> should be a conscious decision, not a copy and paste from a mailing
> list.
>
As is the case with most settings :-)
--
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt,
On Mon, Apr 19, 2010 at 1:07 AM, Johan De Meersman wrote:
> On Mon, Apr 19, 2010 at 6:48 AM, Rob Wultsch wrote:
>>
>> And if your slave's IO lags badly enough this will hose you. Further
>
> True, but if you remove logs that haven't been transferred, yet, you lose
> your slave.
>
> Transfer of lo
Google oom_adj and oom_score. You can control which process is most
likely to be killed.
On Mon, Apr 19, 2010 at 12:53 AM, Johan De Meersman wrote:
>
>
> On Sun, Apr 18, 2010 at 9:04 PM, Eric Bergen wrote:
>>
>> Usually I prefer to have linux kill processes rather than excessively
>> swapping. I
On Mon, Apr 19, 2010 at 6:48 AM, Rob Wultsch wrote:
>
> And if your slave's IO lags badly enough this will hose you. Further
>
True, but if you remove logs that haven't been transferred, yet, you lose
your slave.
Transfer of logs shouldn't be lagging that much, really, unless you're
replicating
On Sun, Apr 18, 2010 at 9:35 PM, Eric Bergen wrote:
> This can become a problem when using replication. For example if you do:
>
> begin;
> insert into innodb_table;
> insert into myisam_table;
> insert into innodb_table;
> rollback;
>
> The innodb rows won't be replicated but the myisam row will
On Sun, Apr 18, 2010 at 9:04 PM, Eric Bergen wrote:
> Usually I prefer to have linux kill processes rather than excessively
> swapping. I've worked on machines before that have swapped so badly
>
I guess you never had the OOM killer randomly shooting down your SSH daemon
on a machine hundred of
Dear All,
I hit belown problem when i compile(make install) 5.5.4-M3 on centos 5.0.
-bash-3.1# cat /etc/redhat-release
CentOS release 5 (Final)
-bash-3.1# uname -a
Linux dbte
16 matches
Mail list logo
