You can use "disable Key" before loading data & use "enable Key " after loading
Command :- alter table {table. Name } disable key;
Same enabling
DK Sent from Phone
On 27-Jun-2013, at 4:57, nixofortune wrote:
> This is my table:
> CREATE TABLE `ga_monthly_keyword_visits` (
> `site_id` int(1
This is the expected behavior if you set the timestamp variable in
your session. This is the same mechanism that replication uses to
execute transactions on the slave with the correct time. Setting
timestamp back to default or reopening your connection will fix it.
MariaDB [(none)]> set timestamp=
On 2013-06-27 01:27, nixofortune wrote:
Now importing with Keys in place. It takes longer, much longer but at
least the server is working and customers do not complaint.
Schema design is awful, agree. I try to understand the process so will
redesign it soon, but any suggestions are welcome.
I'
Well, if you want to get unstuck in time, maybe you need to call Billy
Pilgrim ;-)
Andy Wallace wrote:
We've been having some issues with one of our MySQL servers lately,
and currently
the dang thing is "stuck". For at least the last hour, NOW() is
returning the same
value:
mysql> select now(
> (`site_id`,`index_date`,`index_month`,`index_year`,`keyword`,`source`,`visits`,
>
> `bounced_visits`,`transactions`,`revenue`,`value_per_click`,`conversions`,`goal_value`);
May we see the SHOW CREATE TABLE? Some of this smells bad.
* It is almost always bad to split day/month/year into multip
This is my table:
CREATE TABLE `ga_monthly_keyword_visits` (
`site_id` int(11) DEFAULT NULL,
`index_date` int(11) DEFAULT NULL,
`index_month` int(11) NOT NULL,
`index_year` int(11) NOT NULL,
`keyword` varchar(128) DEFAULT NULL,
`source` varchar(30) DEFAULT NULL,
`visits` int(11) DEFA
Submit a bug:
http://bugs.mysql.com
Alas, you probably cannot provide a reproducible test case. Still, someone
might start at the code and discover a possible cause.
> -Original Message-
> From: Andy Wallace [mailto:awall...@ihouseweb.com]
> Sent: Wednesday, June 26, 2013 3:10 PM
> To: m
2013/06/26 17:31 +0100, nixofortune
ALTER TABLE `new_innodb`
ADD KEY `idx1` (`col1`,`col2`),
ADD KEY `idx2` (`col1`,`col2`,`col3`);
Is it really seemly for one index to be a leading part of another?
(or maybe I am really thinking of something else)
--
MySQL General Mailing Li
We've been having some issues with one of our MySQL servers lately, and
currently
the dang thing is "stuck". For at least the last hour, NOW() is returning the
same
value:
mysql> select now();
+-+
| now() |
+-+
| 2013-06-26 02:27:14 |
+-
You can't actually move innodb tables around until 5.6 where you have
transpotable tablespaces.
I suggest having a good hard look at pt-online-schema-change or whatsitcalled.
Jay Ess wrote:
>On 2013-06-26 18:31, nixofortune wrote:
>> What would be the best way to convert BIG MyISAM table into I
On 25/06/13 23:55, Rick James wrote:
Switch to InnoDB so you won't have to repair after crashes.
Caution: InnoDB takes 2x-3x the disk space per table. Be sure to use
innodb_file_per_table=1.
" Repair by sort." is usually much faster than "repair by keycache"; you probably got
'sort' because o
On 2013-06-26 18:31, nixofortune wrote:
> What would be the best way to convert BIG MyISAM table into InnoDB? We do not
> have SLAVE.
I would do it on another computer. Then copy the table to the server and then
add the data that has been added from the original table.
And/or i would experiment w
12 matches
Mail list logo
