Hi Jørn,
>> I would say that this sort of performance drop is not typical. Some
>> users have reported a smaller performance loss in single threaded
>> workloads in 5.6.
>
> But dropping from an average of 1800 jobs per minute down to 300? I don't
> think that should be expected.
I would agree
On Wednesday 22 January 2014 22:56, you wrote:
> Hi Jørn,
>
> > But I must say I'm not very impressed by the speed. I'm running a test on
> > an application that do a lot of reads and writes queries and the general
> > performance has dropped to 50% of the what I had in 5.5.20.
>
> I would say that
Hi Jørn,
But I must say I'm not very impressed by the speed. I'm running a test on an
application that do a lot of reads and writes queries and the general
performance has dropped to 50% of the what I had in 5.5.20.
I would say that this sort of performance drop is not typical. Some
users hav
On Tuesday 14 January 2014 21:51, Jesper Wisborg Krogh wrote:
> Hi Jørn,
>
> On 15/01/2014 04:36, Jørn Dahl-Stamnes wrote:
> > 140114 18:20:08 InnoDB: Error: data file /data/mysql/data/ibdata3 uses
> > page size 1024,
> > 140114 18:20:08 InnoDB: but the only supported page size in this release
> >
Hi Jørn,
On 15/01/2014 04:36, Jørn Dahl-Stamnes wrote:
140114 18:20:08 InnoDB: Error: data file /data/mysql/data/ibdata3 uses page
size 1024,
140114 18:20:08 InnoDB: but the only supported page size in this release
is=16384
140114 18:20:08 InnoDB: Could not open or create data files.
That erro
e
From: Krishna Chandra Prajapati [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 13, 2008 8:05 AM
To: Eli Shemer
Subject: Re: crash
Hi,
The below information shows that innodb data get crashed and then started
the recovery of data. During recovery of data there was a memory shortage
(Out
]
Sent: Wednesday, February 13, 2008 8:05 AM
To: Eli Shemer
Subject: Re: crash
Hi,
The below information shows that innodb data get crashed and then started
the recovery of data. During recovery of data there was a memory shortage
(Out of memory). At last recovery gets completed.
Thanks
On 31 Aug 2004 at 17:33, Todd O'Bryan wrote:
> I've tested mysql in my high school lab running from an administrator
> and from a student account, both from within the Cygwin terminal, and
> at the Windows command prompt. From the administrator account, it runs
> fine for hours. From the studen
We used to have a fair amount of data in InnoDB.
Had a few crashes from power failures at a crappy hosting provider.
Everytime the InnoDB engine seemed to detect the crashes and read up its
logfiles and recover.
I've never tried any "manual" InnoDB recovery / data extraction. Are there
methods?
Hi there,
I am not sure I understood your question correctly. What exactly is it that
you want to test ?
a) the recovery possibility in case of power down
b) the recovery possibility in case of client disconnection (network
interruption, timeout etc.)
c) Recovery possibilities in general access
Hi,
> Do you know how to test a crash and a rollback?
You mean a client app crashing on you?
How about disabling/unplugging the network?
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 2 Sep 2003, Roman Hochuli wrote:
> i migrated a server of ours (from 3.23) to mysql-4.0.14 (solaris
> 8/sparc/64bit). i took the precompiled binary of the website. so far so
> good.
>
> my problem now is the mysql-server crashed with signal 11
me.
Thanks in advance.
->-Original Message-
->From: Sinisa Milivojevic [mailto:[EMAIL PROTECTED]
->Sent: Saturday, July 19, 2003 6:19 AM
->To: Matt Davies
->Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
->Subject: Re: Crash on mysql_real_connect on FreeBSD 4.7
->
->
-&g
ojevic [mailto:[EMAIL PROTECTED]
->Sent: Saturday, July 19, 2003 6:19 AM
->To: Matt Davies
->Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
->Subject: Re: Crash on mysql_real_connect on FreeBSD 4.7
->
->
->On Fri, 18 Jul 2003 14:22:13 -0600
->"Matt Davies" <[
>
> quick crash-me question
>
> the web page lists several numbers for the performance of several databases (
> MySQL sybase access). The one I'm most insterested in is
> "max table row length"
>
> What does that number symbolize?
>
> The maximum number of bytes in a row? the max number of row
On Friday 20 December 2002 11:01, azerbinati at libero dot it wrote:
> I'd a /etc/hosts misconfigured, it told that the machine name was linux200
> with IP 192.168.0.3 but eth0 was configured to use IP 192.168.0.16. In this
> enviroment executing this command "mysql -h 192.168.0.16" cause a
Mustafa,
Tuesday, September 10, 2002, 10:19:14 AM, you wrote:
MY> we use mysql 3.23.46-max-nt at customer pc. Some customers use Windows2000,
MY> but some use Win98. Mysql Database that run at Win98 platform, sometimes
MY> crashes, and i cannot repair it. The error often ise 144 Error that "TABLE
Hi,
Why don't you just dump the databases, tar.gzip them, and transfer that
file? It's smaller then the .frm+ .myd, and you can rebuild everything
without probs...
MPNeves
On Tuesday 30 July 2002 07:29 am, [EMAIL PROTECTED] wrote:
> MySql crashes:
> On an idle server, executeing
Hello,
I'm not sure if my previous post made it to the list, but it seems that
mysql no longer accepts '.' in database names.
I merely changed the . with _ and the missing databases came alive :)
Kind Regards,
0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0
Stavros Patiniotis wrote:
>Hello,
>
>My hard drive has just failed on my database server, and I have rebuilt it
>and copied the data from backups back on to the drive, however mySQL
>cannot see all of the databases.
>
>A 'show databases' shows all of the databases, however 'use DBNAME' says
>
Hello,
Can you not have '.' in database names any more??
I just renamed one of the databases to something without .'s, and it
worked.
Kind Regards,
0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0
escape net
m a k i n g t h e n e t
Stavros,
As an absolute last resort try the following...
Shutdown mysql first. copy your database backups to a safe place before
doing this.
Removed all tables first off. Then move the .MYD and .MYI and .frm files for
each database.
Run mysqladmin and re-create all of the tables again. and leave
For what it is worth, this does NOT cause 3.23.41 to crash.
On Friday 01 March 2002 3:47 pm, Tony J. White wrote:
> Using versions 3.23.47 or 3.23.49a on linux i386 precompiled binaries.
>
> Using ORDER BY on a column that is type text causes a crash.
>
> The following MySQL Query crashes it's My
On Monday 04 February 2002 07:33 pm, [EMAIL PROTECTED] wrote:
> Version: 4.0.1 binary distro(I have gcc 2.96, so I'm using your prebuilt
one)
> Synopsis: Upon executing a query using the MATCH() clause with FULLTEXT
indicies,
> it will crash the mysqld daemon.
Thanks for the
On Tuesday 22 January 2002 10:21 am, Bernhard Schmalhofer wrote:
> x807b75f handle_segfault__Fi + 383
> ? ? ? ? ?0x812bcaa pthread_sighandler + 154
> ? ? ? ? ?0x8150974 chunk_realloc + 56
> ? ? ? ? ?0x8150907 realloc + 787
> ? ? ? ? ?0x811594e my_realloc + 46
> ? ? ? ? ?0x80fae62 _mi_read_pack_inf
Raffaella,
try to compile the latest version 3.23.46 on your system with the gcc -g
flag. MySQL AB does not have a ready binary on Tru64, so you have to compile
yourself. If it still crashes, run the slave inside gdb and do bt full, so
that we see where it crashes.
Regards,
Heikki
http://www.in
On 2001 Aug 03, Miguel Angel Solórzano <[EMAIL PROTECTED]> wrote:
> I was be able to repeat your bug report. Thanks and it
> will be fixed.
This has been fixed in the current code. Here is a
patch:
*** sql/ha_berkeley.cc.orig Fri Aug 3 09:46:50 2001
--- sql/ha_berkeley.cc Fri Aug 3 09
[EMAIL PROTECTED] writes:
> >Description:
> I`ve compiled the source package 3.23.32.
> CFLAGS="-DHPUX -I/opt/dce/include" CXXFLAGS="-DHPUX -I/opt/dce/include
>-felide-constructors -fno-exceptions -fno-rtti" CXX=gcc ./configure --with-pthread
>--with-named-thread-libs='-ldce' --pr
28 matches
Mail list logo
