On Wed, Aug 27, 2008 at 8:21 PM, Jose Estuardo Avila [EMAIL PROTECTED] wrote:
Hi, I've been trying to find information on how myisam handles locks. I
though myisam had locking only on writes and not on reads.
No, readers block writers. This true of any system that only has read
and write locks
I understand that reads are locked by writes but nowhere does of
mention that reads also block reads. Boy queries y posted to the list
are selects.
Jose E. Avila(tachu)
Yuku/Kickapps
Sent from mobile device.
On Aug 28, 2008, at 5:48 AM, Perrin Harkins [EMAIL PROTECTED] wrote:
On Wed, Aug
In the last episode (Aug 28), Jose Estuardo Avila said:
On Aug 28, 2008, at 5:48 AM, Perrin Harkins wrote:
On Wed, Aug 27, 2008 at 8:21 PM, Jose Estuardo Avila wrote:
Hi, I've been trying to find information on how myisam handles
locks. I though myisam had locking only on writes and not on
On Thu, Aug 28, 2008 at 10:59 AM, Jose Estuardo Avila
[EMAIL PROTECTED] wrote:
I understand that reads are locked by writes but nowhere does of mention
that reads also block reads.
How could they not? You can't simultaneously read and write the same
data -- the read would get half-written
My point is that on my process lists there are no writes being done at
that time only reads and actually only one read all other reads are
locked as well as writes. I've gone through every single one of the
queries in my processlist at any given time when more than 500 process
pile up and
On Thu, Aug 28, 2008 at 1:14 PM, Jose Estuardo Avila [EMAIL PROTECTED] wrote:
My point is that on my process lists there are no writes being done at that
time only reads and actually only one read all other reads are locked as
well as writes.
Sure, that's because the reads are in line behind
Hi, I've been trying to find information on how myisam handles locks.
I though myisam had locking only on writes and not on reads. For some
reason and after a lot of digging i've been seeing that some
queries(albeit bad queries) cause other queries to hang even though
they are selects is
