PROTECTED]
--
Joe Shear [EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Dr. Gregory B. Newby, Research Faculty, Arctic Region Supercomputing Center
University of Alaska Fairbanks. PO Box 756020, Fairbanks, AK 99775
e: newby AT arsc.edu v: 907-474-7160 f: 907-474-5494 w: www.arsc.edu/~newby
--
Joe Shear [EMAIL PROTECTED]
--
MySQL General Mailing
BACK TRANSACTION (2)
--
Joe Shear [EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
transactions.
--
Joe Shear [EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
, and row level locking for MySQL
InnoDB Hot Backup - a hot backup tool for MySQL
Order MySQL technical support from https://order.mysql.com/
- Original Message -
From: Joe Shear [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Friday, September 12, 2003 1:53 AM
Subject
like EMC's -- do you or anybody
else have any experience with that?
Cheers,
Andrew
-Original Message-
From: Joe Shear [mailto:[EMAIL PROTECTED]
Sent: Wednesday 23 July 2003 22:51
To: Andrew Braithwaite
Cc: [EMAIL PROTECTED]
Subject: RE: large mysql/innodb databases
of queries inside InnoDB does not grow. If it grows, then there is a leak
in InnoDB.
MySQL-4.0.14 has better diagnostic prints. It would be easier to find the
problem with it.
Regards,
Heikki
- Original Message -
From: Joe Shear [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED
Hi,
Has anyone ever had any problems with MySQL w/ all InnoDB tables just
stop processing queries? There doesn't seem to be any pattern to it, it
happens at times of relatively high load (load avg of 4 on a dual proc)
but the CPUs still have plenty of idle time, and the disks aren't maxing
out.
if this is the case, when your server gets into this
state run a mysqladmin -v pro and see if all the queries are waiting for a
lock to be freed up.
Hope this helps,
Andrew
-Original Message-
From: Joe Shear [mailto:[EMAIL PROTECTED]
Sent: Wednesday 23 July 2003 19:45
To: [EMAIL
, Heikki Tuuri wrote:
Joe,
- Original Message -
From: Joe Shear [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Wednesday, July 23, 2003 10:40 PM
Subject: RE: mysql stops processing
hi,
We're pretty careful about preventing that. Also, no queries are moving
forward
kind of backup solutions did
you use? We aren't too concerned about the CPU usage as our databases
tend to be i/o bound.
--
Joe Shear [EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
On Wed, 2003-07-23 at 13:11, Heikki Tuuri wrote:
Joe,
- Original Message -
From: Joe Shear [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 11:03 PM
Subject: Re: mysql stops processing
Unfortunately, we haven't been
:)
Cheers,
Andrew
-Original Message-
From: Joe Shear [mailto:[EMAIL PROTECTED]
Sent: Wednesday 23 July 2003 21:08
To: [EMAIL PROTECTED]
Subject: large mysql/innodb databases
I was wondering if anyone had any experience with setting up large and
fairly high performance databases
machines go down, there will still be plenty of fully replicated servers to
satisfy the demand. Make sure that you have UPS so that if the power fails
you can get a clean shutdown. And ignore backups completely.
Hope this helps,
Andrew
-Original Message-
From: Joe Shear
contains
information that should help you find out what is causing the
crash
--
Joe Shear [EMAIL PROTECTED]
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http
Hi,
I'm running mysql 3.23.52 w/ innodb tables, and I started getting some
deadlocks since upgrading from .51. When I do a show innodb status in
prints out the following:
020826 19:22:15 LATEST DETECTED DEADLOCK:
*** (1) TRANSACTION:
TRANSACTION 0 16655549, ACTIVE 1 sec, OS thread id 87339022
A better solution would probably be to implement a form of challenge
response authentication. (IE: Personal Question/Answer). This way, the
attacker has to know the challenge response to even begin the password
change transaction. Additionally, it is a security hole to email anyone
their
It depends on your needs. ENCRYPT, MD5, SHA1 are all hash functions,
which means they are one-way and the SSN can't be recovered. This means
that you can't read their SSN back once they give it to you, you can
only compare something they give you and see if it is the same as the
SSN. This is
I'm using mysql 3.23.51 w/ InnoDB tables, and am running into some
locking issues which I don't believe should occur. There are 2
transactions that seem to interfere with each other. The first
transaction is an update of one table followed by a select of another
table, ie:
BEGIN
UPDATE table1
yes, we are running at serializable, which also explains the locking
problems, especially since we just upgraded from .49.
thanks
joe
On Fri, 2002-08-09 at 15:27, Jeremy Zawodny wrote:
On Fri, Aug 09, 2002 at 02:38:03PM -0700, Joe Shear wrote:
[snip]
COMMIT
we are using the highest
Hi,
I have a mysql database with innodb tables, and I keep running into a
deadlock that is not detected (causes a timeout) and that I don't think
should be happening. Can anyone explain why this is causing a deadlock,
and secondly, how can I fix it or how can I change this so that the
deadlock
21 matches
Mail list logo
