at 1:53 PM, Akshay Suryavanshi
akshay.suryavansh...@gmail.com wrote:
Hello Geetanjali,
Apologies if I have confused you with the normal Select notation. I
meant to write with repeatable-read mode in mind, but looks like that is
not an issue, since you already tested this scenario
Hi Geetanjali,
Well word of caution with this setting, it can block the whole server if
the purge thread is delayed too much. Also look into other things like IO
saturation or issues with disk as to why the purge thread is not able to
keep up with the backlog. If IO is not the issue then there is
primary key, I am able to insert value higher than 30.
Can you please try the same scenario at your end?
Best Regards,
Geetanjali Mehra
Senior Oracle and MySQL DBA Corporate Trainer and Database Security
Specialist
On Tue, Sep 2, 2014 at 1:53 PM, Akshay Suryavanshi
akshay.suryavansh
locking and/or gap locking?
I dont think so.
Please correct me if I am wrong.
Best Regards,
Geetanjali Mehra
Senior Oracle and MySQL DBA Corporate Trainer and Database Security
Specialist
On Fri, Aug 29, 2014 at 11:46 AM, Akshay Suryavanshi
akshay.suryavansh...@gmail.com wrote
Geetanjali,
There is a difference between next-key locking, gap locking and locking
reads.
Next-key locking and gap-locking are used with normal Selects statement in
Innodb, whereas locking reads wont release a lock on the whole column until
transaction completed, and not just selected values.
.
From: Singer Wang [mailto:w...@singerwang.com]
Sent: Thursday, February 14, 2013 3:41 PM
To: Rick James
Cc: Mihail Manolov; Mike Franon; Akshay Suryavanshi;
mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
Its a very pedantic case, but we had a few
Mike,
5.6 is GA now, so its stable release. Also you should not jump to 5.6
directly, atleast from 5.0.
There are many bug fixes and changes in 5.1, so you should consider this
way.
5.0--5.1--5.5 (all slaves first, and then the master)
And further 5.5 -- 5.6 (again all slaves first and then
Hi,
Please re-phrase your question. The relay logs are created as and when
required by the Slave_SQL thread. Once all the events in the relay logs are
executed the relay log would be purged by the Slave_SQL thread.
By setting relay_log_purge=0 you are disabling this automatic purge option.
So
Also, you may want to see, if at all new file is really getting every hour
exactly, if any cron'd script runs, which executes flush logs on the
slave server. That will also rotate relay log.
Cheers
On Wed, Jan 9, 2013 at 1:35 AM, Akshay Suryavanshi
akshay.suryavansh...@gmail.com wrote:
Hi
:
- Original Message -
From: Akshay Suryavanshi akshay.suryavansh...@gmail.com
I am not sure, but if its a MyISAM table, it should be ordered by the
records insertion order, and in case of InnoDB it should be ordered
by the clustered index, not necessarily it should be a defined one
I am not sure, but if its a MyISAM table, it should be ordered by the
records insertion order, and in case of InnoDB it should be ordered by the
clustered index, not necessarily it should be a defined one.
On Thu, Dec 13, 2012 at 12:58 PM, jiangwen jiang jiangwen...@gmail.comwrote:
hi, all:
Hi,
A subquery with IN clause is not a good idea. If you want to tune this
query, try adding indexes on the tables accessed in the inner query
credits. A composite index on (success,promoter_id) would be sufficient,
then the optimizer will use this index for the where clause and as a
covering
Hi,
This table can be repaired using Repair table table_name; in mysql.
This should fix the corrupted index file, or if mysql is shutdown, you can
run myisamchk, also if its a myisam table.
Hope this helps.
Regards,
Akshay S
On Fri, Oct 19, 2012 at 11:52 AM, a bv vbavbal...@gmail.com wrote:
Hi,
Check the transactions which are causing locks. Use show engine innodb
status \G to find out the transactions acquiring locks for so long. As the
scenario you mentioned (like you use innodb at simpler level), you might be
in a situation where there are SELECTs causing the issue.
It is
by adding the secondary indexes after the
data import or such alters are complete.
Regards,
Akshay Suryavanshi
On Fri, Sep 28, 2012 at 1:56 AM, Rick James rja...@yahoo-inc.com wrote:
Isn't ALTER a DDL, not DML? So I don't think you would find anything in
undo logs.
-Original Message
:37 PM, Akshay Suryavanshi
akshay.suryavansh...@gmail.com wrote:
Hi,
The alter taking such a long time, could be due to composite indexes on
the
table.
There are 22 indexes on the table, but none are composites.
we understand the table is big but not so big to take such a long
time
Hi,
If you dont have data on the server, would you please initialize the data
directory.
Use mysql-install-db and give proper data directory and proper cnf file if
you are giving so.
Also specify the user as root if you have root access.
Thanks
On Mon, Sep 10, 2012 at 3:34 PM, Machiel
Hi,
If you can afford try changing the tmpdir for mysql. This is a static
variable and will require a mysql restart.
thanks
On Mon, Sep 10, 2012 at 6:08 PM, Machiel Richards - Gmail
machiel.richa...@gmail.com wrote:
Hi
at the moment this does not really matter to us.
we have even
with connect.
Thanks
Akshay Suryavanshi
On Mon, Jul 16, 2012 at 8:51 AM, Tim Dunphy bluethu...@gmail.com wrote:
hello,
currently my php app is failing logins to it's mysql database. My config
file is set like this:
[mysqld_safe]
general-log=1
general-log-file=/var/log/mysqld-general.log
log
Hi,
The statement will do a Full table scan, because of the following things :
Not using Where clause, and selecting all columns (*) within the query.
Filesort is used since no index is used, use a where clause with condition
on column which is indexed and notice the explain plan. Also you can
20 matches
Mail list logo
