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
connect.
Thanks
Akshay Suryavanshi
On Mon, Jul 16, 2012 at 8:51 AM, Tim Dunphy 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-
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 Richards
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
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 wrote:
> Isn't ALTER a DDL, not DML? So I don't think you would find anything in
> undo logs.
>
> > -Origi
This appears to be statistics over the life of the invocation of the
> server, correct? But using 405.80 inserts/s give that the alter will
> take almost 79 hours.
>
> >
> > Usually, you carry this operation by adding the secondary indexes after
> the
> > data import
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 strange
Hi,
This table can be repaired using Repair table ; 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 wrote:
> Hi on a log management server
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 in
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 wrote:
> hi, all:
>
> There's a confusion
l Message -
> > From: "Akshay Suryavanshi"
> >
> > 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 def
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 the
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..
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
far, but it still checking, my database is
> >>>>> huge so might be a while.
> >>>>>
> >>>>> The question I have what is the best way to fix this?
> >>>>>
> >>>>> To install all I did was remove all of the 5.0, and
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.
M
lect where..between
>
> Does above select statement will use next-key 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 an
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
ted (0.00 sec)
>
>
>
>
>
> I tried the above scenario with index and without index. Without index
> it is showing the same behaviour as before. Using non-unique index, it is
> not locking the next value (20)immediately after the gap. But it is locking
> a row with id=6, the
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
20 matches
Mail list logo
