2013/3/24 Reindl Harald h.rei...@thelounge.net
Am 24.03.2013 05:20, schrieb spameden:
2013/3/19 Rick James rja...@yahoo-inc.com:
you never have hosted a large site
Check my email address before saying that.
:D
as said, big company does not have only geniusses
I do not judge only
Am 02.04.2013 16:09, schrieb spameden:
2013/3/24 Reindl Harald h.rei...@thelounge.net
mailto:h.rei...@thelounge.net
Am 24.03.2013 05:20, schrieb spameden:
2013/3/19 Rick James rja...@yahoo-inc.com
mailto:rja...@yahoo-inc.com:
you never have hosted a large site
Check
use DBI;
my $dbh = DBI-connect( DBI:mysql:rushload;192.168.0.1, $usrr, $passw, {
RaiseError = 3 } );
my $dbs = $dbh-selectcol_arrayref(show databases);
#my $dsn = dbi:mysql:information_schema:192.168.0.1:3306;
#my $dbh = DBI-connect($dsn, $usrr, $passw);
my $dbs = $dbh-selectcol_arrayref('show
I did a GRANT REPLICATION SLAVE ON *.* TO 'user'@'192.168.0.23' IDENTIFIED
BY 'psswd';
on the master. Doesn't *.* mean everything? Why would it just show me to
databases?
2013/4/2 Larry Martell larry.mart...@gmail.com
On Tue, Apr 2, 2013 at 11:30 AM, Richard Reina gatorre...@gmail.com
On Tue, Apr 2, 2013 at 11:30 AM, Richard Reina gatorre...@gmail.com wrote:
use DBI;
my $dbh = DBI-connect( DBI:mysql:rushload;192.168.0.1, $usrr, $passw, {
RaiseError = 3 } );
my $dbs = $dbh-selectcol_arrayref(show databases);
#my $dsn = dbi:mysql:information_schema:192.168.0.1:3306;
#my
Nope. That's just granting replication privileges so it can read updates
on all tables on all databases. It cannot select anything.
Why are you trying to connect with a replication slave user?
On 4/2/13 1:47 PM, Richard Reina gatorre...@gmail.com wrote:
I did a GRANT REPLICATION SLAVE ON
Am 02.04.2013 22:56, schrieb Rick James:
I hear that nginx is very fast for a certain class of web serving.
yes
But what happens if a web page needs to do a SELECT?
what should happen?
Is nginx single-threaded, thereby sitting idle waiting for the SELECT?
why should it do that?
(Thanks for the comment, spameden.)
Well, I was going to drop the thread, but he baited me. I _do_ know something
about web serving...
Should I recount the number of times I have traced a database meltdown back to
MaxClients being too big? They are _ugly_ meltdowns -- hundreds of
Am 02.04.2013 23:15, schrieb Rick James:
SELECT is not performed in the same thread as nginx; it is performed in
another process, or even (in big web setups) in a different host. Therefore,
nginx would be in some form of wait state, thereby not really using the CPU.
tell me something new
SELECT is not performed in the same thread as nginx; it is performed in another
process, or even (in big web setups) in a different host. Therefore, nginx
would be in some form of wait state, thereby not really using the CPU.
-Original Message-
From: Reindl Harald
I hear that nginx is very fast for a certain class of web serving. But what
happens if a web page needs to do a SELECT? Is nginx single-threaded, thereby
sitting idle waiting for the SELECT? And, should you run 8 nginx web servers
on an 8-core box?
-Original Message-
From:
2013/4/3 Rick James rja...@yahoo-inc.com
SELECT is not performed in the same thread as nginx; it is performed in
another process, or even (in big web setups) in a different host.
Therefore, nginx would be in some form of wait state, thereby not really
using the CPU.
ofc select is not
2013/3/28 Rafał Radecki radecki.ra...@gmail.com
Hi All.
I have a production setup of four databases connected with
replication. I would like to log every command that clients execute
for auditing.
Take a look at general query log it's exactly what you need.
Am 02.04.2013 23:14, schrieb Rick James:
(Thanks for the comment, spameden.)
Well, I was going to drop the thread, but he baited me. I _do_ know
something about web serving...
maybe
Should I recount the number of times I have traced a database meltdown back
to MaxClients being too big?
14 matches
Mail list logo
