Howdy,
I'm looking for ways to better enforce user password security through
MySQL. Currently, it does not appear that there are any restrictions on
minimum length, password expiration times or strong password checking.
Other than educating the users directly, is there a way to enforce any
or
I use memlock to ensure it stays in memory. More than likely it's table
optimization. EXPLAIN and SHOW INDEXES will likely help you once you
turn slow query logging on.
-J
-Original Message-
From: Justin Swanhart [mailto:[EMAIL PROTECTED]
Sent: Monday, August 16, 2004 3:24 PM
To:
-Original Message-
From: Egor Egorov [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 04, 2004 8:33 AM
To: [EMAIL PROTECTED]
Subject: Re: CREATE performance degradation from 4.0.17 - 4.0.20
Sergei Golubchik [EMAIL PROTECTED] wrote:
As one usually doesn't create tables at the huge
On other hand B-C changes for some tests surprise me. Are the
results stable if you repeat the run ? In some cases especially
for short tests deviation can be pretty large.
The results are stable, sadly. The bigger surprise was the select
deviation from 3 to 4, but so far, in application
We're upgrading from 3.23.58 to 4.0.20 and found that that although the
ALTER test results of sql-bench had been greatly improved, CREATE has
shown nasty performance degradation. Just before needing to make the
decision to revert back to 3.23.58, we found a post here where someone
had a similar
