Justin wrote:
lockup just happened again.. here's a innodb status.
InnoDB status will be basically useless, as full-text is only applicable
to MyISAM, and indeed your status output shows only one transaction is
running (the one running 'show innodb status') and InnoDB has done zero
work sinc
Andrew Braithwaite wrote:
Does anyone know if thread_concurrency works in linux or is it just
limited to Solaris and Windows?
Hi! That variable only affects Solaris, as the Solaris threading
library supports thr_setconcurrency().
innodb_thread_concurrency, however, can affect all platforms,
In the last episode (Sep 03), Marten Lehmann said:
> I couldn't find an option within mysql 5.0.x to get a dump of all
> rows of a table with one line per row/record. I always get insert
> statements with all rows at once. Has that option been removed since
> 4.1.x?
Add --skip-extended-insert to y
lockup just happened again.. here's a innodb status.
mysql> show innodb status;
|
=
070903 12:22:31 INNODB MONITOR OUTPUT
=
Per second averages calculated from the last 21 seconds
--
SEMAPHORES
--
OS WAIT ARR
Hello Lucio,
Thank you for the excellent description of you problem. I believe I
completely understand both the data you are handling and the problems
you are facing.
I would not ask you to change your schema at this point. There is far
too much work put into it at this phase to suggest a re
Hello,
I couldn't find an option within mysql 5.0.x to get a dump of all rows
of a table with one line per row/record. I always get insert statements
with all rows at once. Has that option been removed since 4.1.x?
Regards
Marten
--
MySQL General Mailing List
For list archives: http://lists.
As I'm new on this list and can't find a "policy statement", I assume it
is OK to reply to the list in "discussion list" fashion. If instead it is
preferred to reply to each sender privately and later I'd post a summary,
please let me know and I'll comply.
On Sat, 1 Sep 2007, Shawn Green wrote:
