Hi.
I setup two masters to replicatin with each other, say A and B.
A's server id is 1, B's id is 2.
then because of some reason, I must change A's server id to 11. I do
it by changing options in my.cnf and restaring mysql sever.
but a problem happened: A and be make up a LOOP.
that is, when A
So how bad is this? The mentioned query will be the query which is used
the most in my application (yes, it is going to be a forum).
Should I break normalization and save the date of the root in each node
row?
My recommendation is no. Normalization is a Good Thing, and you'll be
Hi list,
I need to store what is basically a key-value pair. A few years ago i would
have choosen
an integer as key and used a translation table to get the name (char[]) for the
key.
Since diskspace is plenty i thinking about to use the name directly. does
anyone has any idea
what is the
On Fri, Aug 29, 2008 at 4:57 AM, walter harms [EMAIL PROTECTED] wrote:
Since diskspace is plenty i thinking about to use the name directly. does
anyone has any idea
what is the performance penalty ?
hey,
I have been playing with different ways to improve diagnostic and audit data
in MySQL that don't necessarily involve source mods (ex. general log to fifo
w/background parser/logger). I've come up w/the following way of logging
connections to give similar data to the listener.log file in
thx,
the results support my suspect
re,
wh
Perrin Harkins schrieb:
On Fri, Aug 29, 2008 at 4:57 AM, walter harms [EMAIL PROTECTED] wrote:
Since diskspace is plenty i thinking about to use the name directly. does
anyone has any idea
what is the performance penalty ?
-Original Message-
From: Kevin Hunter [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 28, 2008 10:59 PM
To: John Smith
Cc: MySQL General List
Subject: Re: Normalization vs. Performance
At 2:11pm -0400 on Tue, 26 Aug 2008, John Smith wrote:
So how bad is this? The mentioned query will be
Yours is the classic case of the distinction between OLTP and OLAP, and in
my opinion you are doing it exactly right. For analysis purposes,
de-normalization is a good thing because you eliminate the joins and
increase performance, but even more important, you don't slow down the
data-entry
addresses the case for using ENUM over VARCHAR for low cardinality columns
For performance issues on which sort algorithm does a join select is addressed
at
http://dev.mysql.com/doc/refman/5.0/en/index-merge-optimization.html
?
Martin
__
Disclaimer
Again, sorry for cross-posting, but might be of interest to both the
general and win32 mailing lists.
The MyQuery MySQL scripting tool has advanced into version 2.0 and has
turned into a reasonably full-features query tool. Version 2.0
introduces syntax highlightning, search and replace and
could'nt get database listings to display..all other commands and requests seem
to work fine
Tack!
Martin
__
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business
of Sender. This
Hi,
When I read Jk's document on MySQL proxy:
http://jan.kneschke.de/projects/mysql/mysql-proxy/
In Load balancing part, he mentioned that:
We use SQF (shortest queue first) to distribute the load across the
backends equally. Each backend will get the same number of connections.
My
12 matches
Mail list logo
