My apologies for missing the previous discussion and thanks for the info. A follow up
question: is there a performance penalty associated with using PreparedStatement's
with queries that will never be reused? Clearly, there's a performance benefit for
statements executed multiple times, but ho
Is there a 'global' way to tell MySQL to not interpret the backslashes ('\'s) in the
submitted SQL as escape characters? In other words, I'd like for them to always be
treated as if they themselves were already escaped with a backslash (i.e. '\\'). I'm
using 3.23.52, accessing it with an older
Hello Heikki,
Thanks for your response. Hmmm... When I run 'show processlist', I get something
like the following:
++--++--+-+-+---+--+
| Id | User | Host | db | Command
Hello Heikki,
> why you do not look with SHOW INNODB STATUS if there are dangling
> transactions which could still see the delete-marked rows? Purge cannot
> remove them then.
This is what I see:
mysql> show table status like 'sccchangelog';
+--++++---
Hi,
I wanted to post a follow-up question to the inquiry below. I've done some more
research since my last post and now think that the performance problem is related to
something other than uncommitted transactions. More specifically, I think the culprit
is the lack of timely synchronization
