On Sat, May 10, 2008 at 4:24 PM, JW <[EMAIL PROTECTED]> wrote:
>> Table locking will occur with MyISAM tables when any row(s) of the table is
>> being updated (Update,Delete,Insert,Load Data etc).
>> If you are only executing Select statements, then they can be executed in
>> parallel and won't be
> Table locking will occur with MyISAM tables when any row(s) of the table is
> being updated (Update,Delete,Insert,Load Data etc).
> If you are only executing Select statements, then they can be executed in
> parallel and won't be blocked.
Just curious: you say "with MyISAM tables" - do any of t
At 05:05 PM 5/9/2008, you wrote:
On Friday 09 May 2008 04:32:10 pm Saravanan wrote:
> --- On Sat, 5/10/08, JW <[EMAIL PROTECTED]> wrote:
> > From: JW <[EMAIL PROTECTED]>
> > Is it correct that mysql 5.0 is threaded in such a way that
> > a DB server taking lots of queries from many clients will b
On Friday 09 May 2008 04:32:10 pm Saravanan wrote:
> --- On Sat, 5/10/08, JW <[EMAIL PROTECTED]> wrote:
> > From: JW <[EMAIL PROTECTED]>
> > Is it correct that mysql 5.0 is threaded in such a way that
> > a DB server taking lots of queries from many clients will be able\
> > to utilize lots of CPUs
TECTED]
> Sent: Wednesday, December 01, 2004 11:22 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Table Locking Problem? Very Slow MyISAM DB - PLS HELP!
>
>
> >The reason I ask is because eight select statements should not bog down a
> >production serve
When the server begins to slow down, what does top reveal?
Andrew Nelson wrote:
The reason I ask is because eight select statements should not bog
down a production server. On the MySQL side, is anything being
written to the slow query log? On the application side is there any
virus scanning or
The reason I ask is because eight select statements should not bog down a
production server. On the MySQL side, is anything being written to the slow
query log? On the application side is there any virus scanning or similar
activity being performed? Does iostat show any heavy reading or writing
The reason I ask is because eight select statements should not bog down
a production server. On the MySQL side, is anything being written to the
slow query log? On the application side is there any virus scanning or
similar activity being performed? Does iostat show any heavy reading or
writing
Hi Victor,
How did you deduce that the database server is the bottleneck? Are all your
processes running on the same machine?
Because 'ps -aux' shows it running at 94% of the CPU and when I
stop/start the mysql server, it seems to be ok again for another
hour.
Any ideas?
Andrew Nelson wrote:
Hi
How did you deduce that the database server is the bottleneck? Are all
your processes running on the same machine?
Andrew Nelson wrote:
Hi,
I have a MySQL 3.23.55 server managing accounts on my exim mail server..
The table type on all tables MyISAM.. I have the MTA performing
various queries
fo
Hi Andy,
The best way to accomplish this is at an application level, setup a
lock table and put your locks in there. There are many methods for
handling application locks. Choose one that work for you. With a
database level lock, when the connection terminates the lock is
released.
Persistant c
Andy Ford wrote:
I have a perl cgi script that needs to lock the tables. Unfortunately,
as HTTP is a one shot protocol, once the cgi script completes execution,
the tables are unlocked.
I need it to stay locked until another cgi script unlocks them!
Is there any other way of achieving this!?
You c
On Mon, Aug 18, 2003 at 11:15:31AM -0700, [EMAIL PROTECTED] wrote:
> I could fix this if I changed the table type to InnoDB, correct?
Yes.
InnoDB uses a very different locking model. You'll get very good
read/write concurrency with InnoDB.
Jeremy
--
Jeremy D. Zawodny | Perl, Web, MySQL, L
I could fix this if I changed the table type to InnoDB, correct?
-James
Quoting Jeremy Zawodny <[EMAIL PROTECTED]>:
> On Mon, Aug 18, 2003 at 10:41:55AM -0700, [EMAIL PROTECTED] wrote:
> > Hello,
> >
> > I just have a question about the table locking in 3.23.56. If I am
> inserting a
> > row i
On Mon, Aug 18, 2003 at 10:41:55AM -0700, [EMAIL PROTECTED] wrote:
> Hello,
>
> I just have a question about the table locking in 3.23.56. If I am inserting a
> row into a table that is MyISAM type, is the entire table locked?
Yes.
> And, if so, what does this mean for concurrent selects?
An I
In the last episode (Aug 18), [EMAIL PROTECTED] said:
> I just have a question about the table locking in 3.23.56. If I am
> inserting a row into a table that is MyISAM type, is the entire table
> locked? And, if so, what does this mean for concurrent selects?
Inserting a row into a full table doe
-->-Original Message-
-->From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
-->Sent: Monday, August 18, 2003 10:42 AM
-->To: [EMAIL PROTECTED]
-->Subject: Table locking...
-->
-->Hello,
-->
-->I just have a question about the table locking in 3.23.56. If I am
-->inserting a
-->row into a t
At 8/15/2002, you wrote:
>Hi everyone!
>
>I'm fairly familiar with the table locking methods in MySQL but I have a
>problem I can't solve.
>
>I have two main tables which are read simultaneously by many clients. The
>clients only do reads, but they do it very extensively and for 30 secs each.
>
>T
I had put a similar question (that unfortunately never got answered) on
this mailing list and so I have pondered about this problem also. The
way I see it, delayed_insert_timeout doesn't do any good here because it
only determines how long an idle (with no pending jobs) insert delayed
thread will
lorenzo.kh,
Monday, July 29, 2002, 11:59:49 AM, you wrote:
lk> I have a question regard the table locking.
lk> Let say there is a table ,mytablename type=MyISAM in my database.
lk> And lets say there are 2 users who are currently log in.
lk> First user locks a table write:
lk> mysql> lock tables
if you need table or datarow locking , why don't you use innodb table type
with transactions ?
bye, thomas
> First user locks a table write:
> mysql> lock tables mytablename write;
> Query OK, 0 rows affected (0.00 sec)
>
> Then,second user wishes to query something from mytablename.
> mysql>sele
On Fri, Dec 21, 2001 at 12:45:16PM -0800, Shannon Kendrick wrote:
: Whats the drawback of using InnoDB instead of MySAM
: tables?
Tables aren't kept in separate files, disk space preallocated,
little less mature (but no less stable, I've found). For most
people, those aren't drawbacks, just diff
Whats the drawback of using InnoDB instead of MySAM
tables?
--- Carl Troein <[EMAIL PROTECTED]> wrote:
>
> Shannon Kendrick writes:
>
> > Does anyone know of a way to lock at the row level
> > instead of table level using MySQL 3.23.46
>
> Yep, use InnoDB instead of MyISAM tables.
>
> //C - p
Whats the drawback of using InnoDB instead of MySAM
tables?
--- Carl Troein <[EMAIL PROTECTED]> wrote:
>
> Shannon Kendrick writes:
>
> > Does anyone know of a way to lock at the row level
> > instead of table level using MySQL 3.23.46
>
> Yep, use InnoDB instead of MyISAM tables.
>
> //C - p
Shannon Kendrick writes:
> Does anyone know of a way to lock at the row level
> instead of table level using MySQL 3.23.46
Yep, use InnoDB instead of MyISAM tables.
//C - person of few words. But surprisingly seldom.
--
Carl Troein - Círdan / Istari-PixelMagic - UIN 16353280
[EMAIL PROTECT
Hi.
Please stop cross-posting and use the appropriate forum.
On Wed, Nov 21, 2001 at 03:27:23PM -0700, [EMAIL PROTECTED] wrote:
>
> (PHP-DB folks, ignore this top question - unless you want to answer)
>
> Which type of DB/Table provides table locking while a process is
> altering data?
Thanks Gerald,
I finally figured that out, from what I understand, when locking and the given
table is set to 'WRITE' this includes 'READ' too. so I only needed to use the
table once :)
Cheers,
>>On Fri, 03 Aug 2001 14:31:00 -0500, Gerald Clark <[EMAIL PROTECTED]>
> wrote:
>>
>>> Hi All,
>>
ame field is text and number so you I can't autoincrement a
> username like "abc003434" ...
>
>
> - Original Message -
> From: "Mohammad Shoja" <[EMAIL PROTECTED]>
> To: "anna soobrattee" <[EMAIL PROTECTED]>
> Sent:
Hi,
The username field is text and number so you I can't autoincrement a
username like "abc003434" ...
- Original Message -
From: "Mohammad Shoja" <[EMAIL PROTECTED]>
To: "anna soobrattee" <[EMAIL PROTECTED]>
Sent: Wednesday, June 1
http://www.mysql.com/doc/I/n/Internal_locking.html
Hope this helps.
-- Rodney
Zach Hollandsworth wrote:
> Is there an explanation somewhere about the rules mysql uses when lock
> tables?
>
> -
> Before posting, please check:
>
On Tue, Jan 16, 2001 at 08:30:01AM -0500, Jeff Lewis wrote:
> I have always used flat file text files for my database purposes but
> this has always led to problems when the number of users gets to be
> too many.
Tell me about it. I converted a system like that to MySQL a while
back. It's s
31 matches
Mail list logo
