[mythtv-users] Slow MySQL query after delete
Jay R. Ashworth
jra at baylink.com
Wed Sep 5 15:25:15 UTC 2007
On Wed, Sep 05, 2007 at 01:36:11AM -0700, David Rees wrote:
> On 9/4/07, Michael T. Dean <mtdean at thirdcontact.com> wrote:
> > Basically, one of the biggest benefits is that we could move all efforts
> > to supporting embedded MySQL 5.5 or whatever and could drop support for
> > MySQL 3.23, MySQL 4.0, MySQL 4.1, MySQL 5.0, ... There's a /lot/ of
> > performance-draining "backwards compatibility" in the code we have now.
> > If all users had the same DB engine, things would be a /lot/ easier.
> You really should think about dropping support for anything older than
> 4.1. What's the point in maintaining anything that the upstream vendor
> doesn't support themselves?
So that my point (from another part of the thread) is clear:
I can live with them not ever making it possibel to run atop PgSQL.
I would be *much* less happy if they switched to *only* being able to
use *Embedded* MySQL (as opposed to the standalone version --
*particularly* if it made it impossible to use said standalone version
on the same machine -- and I am clearly not alone.
(MySQL is pretty promiscuous about which my.cnf to read; it can cause
problems trying to run 2 on one box.)
Jay R. Ashworth Baylink jra at baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://baylink.pitas.com '87 e24
St Petersburg FL USA http://photo.imageinc.us +1 727 647 1274
More information about the mythtv-users