Re: MySQL daemons restarting every 7 minutes

[Suresh Kuna]

can you check for any table crashes in the db by using mysqlcheck.

and enable the general log for the database.

On Fri, Sep 9, 2011 at 10:37 PM,  wrote:

> No need for that really is there? I posted what was requested.
> The part for the shutdown:
>
> 110909 17:27:31  InnoDB: Starting shutdown...
> 110909 17:27:32  InnoDB: Shutdown completed; log sequence number 1589339
> 110909 17:27:32 [Note] /usr/local/libexec/mysqld: Shutdown complete
>
> 110909 17:27:32 mysqld_safe mysqld from pid file /var/db/mysql/tau.pid
> ended
>
> 110909 17:27:35 mysqld_safe Starting mysqld daemon with databases from
> /var/db/mysql
> 110909 17:27:35 InnoDB: The InnoDB memory heap is disabled
> 110909 17:27:35 InnoDB: Mutexes and rw_locks use GCC atomic builtins
> 110909 17:27:35 InnoDB: Compressed tables use zlib 1.2.3
> 110909 17:27:35 InnoDB: Initializing buffer pool, size = 2.0G
> 110909 17:27:36 InnoDB: Completed initialization of buffer pool
> 110909 17:27:36 InnoDB: highest supported file format is Barracuda.
> 110909 17:27:36  InnoDB: Waiting for the background threads to start
> 110909 17:27:37 InnoDB: 1.1.8 started; log sequence number 1589339
> 110909 17:27:37 [Note] Slave SQL thread initialized, starting replication
> in log 'mysql-bin.002830' at position 293541, relay log
> './tau-relay-bin.000920' position: 253
> 110909 17:27:37 [Note] Event Scheduler: Loaded 0 events
> 110909 17:27:37 [Note] /usr/local/libexec/mysqld: ready for connections.
> Version: '5.5.15'  socket: '/tmp/mysql.sock'  port: 3306  Source
> distribution
> 110909 17:27:37 [Note] Slave I/O thread: connected to master
> 'slave_user@kappa:3306',**replication started in log 'mysql-bin.002830' at
> position 293541
>
>
>
>
>
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:http://lists.mysql.com/mysql?**
> unsub=sureshkumar...@gmail.com
>
>


-- 
Thanks
Suresh Kuna
MySQL DBA

Re: Update on inner join - looks good to me, where did I go wrong?

[Carsten Pedersen]

`userTable.userid` => `userTable`.`userid`

/ Carsten

On 09-09-2011 23:01, Dotan Cohen wrote:

Now that I've got the syntax right, MySQL is complaining that a field
does not exist, which most certainly does:

mysql>  UPDATE
 ->   `userTable`
 ->  INNER JOIN `anotherTable`
 ->ON `userTable.userid`=`anotherTable.userid`
 ->  SET `userTable.someField`="Jimmy Page"
 ->  WHERE `userTable.someField`="Jim Morrison"
 ->AND `anotherTable.date`<  NOW();
ERROR 1054 (42S22): Unknown column 'userTable.someField' in 'field list'
mysql>
mysql>  SELECT count(someField) FROM userTable;
+---+
| count(someField) |
+---+
|  5076 |
+---+
1 row in set (0.00 sec)

mysql>

What could be the issue here? Thanks!




--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: Update on inner join - looks good to me, where did I go wrong?

[Dotan Cohen]

Now that I've got the syntax right, MySQL is complaining that a field
does not exist, which most certainly does:

mysql> UPDATE
->  `userTable`
-> INNER JOIN `anotherTable`
->   ON `userTable.userid`=`anotherTable.userid`
-> SET `userTable.someField`="Jimmy Page"
-> WHERE `userTable.someField`="Jim Morrison"
->   AND `anotherTable.date` < NOW();
ERROR 1054 (42S22): Unknown column 'userTable.someField' in 'field list'
mysql>
mysql> SELECT count(someField) FROM userTable;
+---+
| count(someField) |
+---+
|  5076 |
+---+
1 row in set (0.00 sec)

mysql>

What could be the issue here? Thanks!


-- 
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Update on inner join - looks good to me, where did I go wrong?

[Dotan Cohen]

I'm trying to update on an join, but I can't find my error:

UPDATE `userTable`
SET `someField`="Jimmy Page"
FROM `userTable` INNER JOIN `anotherTable`
  ON `userTable.userid`=`anotherTable.userid`
WHERE `userTable.someField`="Jim Morrison"
  AND `anotherTable.date` < NOW();

ERROR 1064 (42000): You have an error in your SQL syntax; check the
manual that corresponds to your MySQL server version for the right
syntax to use near 'FROM

That error is for reserved words, and I am escaping all the fields and
tables (using the backticks). So why the error?

This is on a CentOS 4 or 5 server, with MySQL 5.0.77, accessed from
the CLI. Thanks!


-- 
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: MySQL daemons restarting every 7 minutes

[a . smith]

No need for that really is there? I posted what was requested.
The part for the shutdown:

110909 17:27:31  InnoDB: Starting shutdown...
110909 17:27:32  InnoDB: Shutdown completed; log sequence number 1589339
110909 17:27:32 [Note] /usr/local/libexec/mysqld: Shutdown complete

110909 17:27:32 mysqld_safe mysqld from pid file /var/db/mysql/tau.pid ended
110909 17:27:35 mysqld_safe Starting mysqld daemon with databases from  
/var/db/mysql

110909 17:27:35 InnoDB: The InnoDB memory heap is disabled
110909 17:27:35 InnoDB: Mutexes and rw_locks use GCC atomic builtins
110909 17:27:35 InnoDB: Compressed tables use zlib 1.2.3
110909 17:27:35 InnoDB: Initializing buffer pool, size = 2.0G
110909 17:27:36 InnoDB: Completed initialization of buffer pool
110909 17:27:36 InnoDB: highest supported file format is Barracuda.
110909 17:27:36  InnoDB: Waiting for the background threads to start
110909 17:27:37 InnoDB: 1.1.8 started; log sequence number 1589339
110909 17:27:37 [Note] Slave SQL thread initialized, starting  
replication in log 'mysql-bin.002830' at position 293541, relay log  
'./tau-relay-bin.000920' position: 253

110909 17:27:37 [Note] Event Scheduler: Loaded 0 events
110909 17:27:37 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.5.15'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110909 17:27:37 [Note] Slave I/O thread: connected to master  
'slave_user@kappa:3306',replication started in log 'mysql-bin.002830'  
at position 293541







--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: MySQL daemons restarting every 7 minutes

[Reindl Harald]

jesus christ can you post a WHOLE log
this is only a normal start, there is no single line about stop

Am 09.09.2011 18:30, schrieb a.sm...@ukgrid.net:
> Yep, but its basically identical to the info in the logs when its restarting 
> itself. I have upgraded to MySQL 5.5
> as of yesterday, so the error info differs due to the version now. Here is 
> the log output:
> 
> 110909 17:27:35 mysqld_safe Starting mysqld daemon with databases from 
> /var/db/mysql
> 110909 17:27:35 InnoDB: The InnoDB memory heap is disabled
> 110909 17:27:35 InnoDB: Mutexes and rw_locks use GCC atomic builtins
> 110909 17:27:35 InnoDB: Compressed tables use zlib 1.2.3
> 110909 17:27:35 InnoDB: Initializing buffer pool, size = 2.0G
> 110909 17:27:36 InnoDB: Completed initialization of buffer pool
> 110909 17:27:36 InnoDB: highest supported file format is Barracuda.
> 110909 17:27:36  InnoDB: Waiting for the background threads to start
> 110909 17:27:37 InnoDB: 1.1.8 started; log sequence number 1589339
> 110909 17:27:37 [Note] Slave SQL thread initialized, starting replication in 
> log 'mysql-bin.002830' at position
> 293541, relay log './tau-relay-bin.000920' position: 253
> 110909 17:27:37 [Note] Event Scheduler: Loaded 0 events
> 110909 17:27:37 [Note] /usr/local/libexec/mysqld: ready for connections.
> Version: '5.5.15'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
> 110909 17:27:37 [Note] Slave I/O thread: connected to master 
> 'slave@kappa:3306',replication started in log
> 'mysql-bin.002830' at position 293541
> 
> Just not giving any hit of a problem
> 
> thanks Andy.
> 
> Quoting Suresh Kuna :
> 
>> can you remove it from service and start it normally using mysqld_safe with
>> log warnings enabled in the cnf file.
>>
>> On Fri, Sep 9, 2011 at 4:16 PM,  wrote:
>>
>>> Hi,
>>>
>>>  that really is the complete error log, that exact same info gets repeated
>>> over and over, there is zero in the syslog and I get this behaviour when
>>> running with no my.cnf (I do obviously have one but I tried without and it I
>>> still see the prob, so that probably makes things easier from a
>>> troubleshooting perspective)...
>>> The system has loads of free RAM (8GB total).
>>> Really the system isn't giving me much to go in in terms of clues
>>>
>>> Andy.
> 
> 
> 
> 
> 

-- 

Mit besten Grüßen, Reindl Harald
the lounge interactive design GmbH
A-1060 Vienna, Hofmühlgasse 17
CTO / software-development / cms-solutions
p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40
icq: 154546673, http://www.thelounge.net/

http://www.thelounge.net/signature.asc.what.htm



signature.asc
Description: OpenPGP digital signature

Re: MySQL daemons restarting every 7 minutes

[a . smith]

Yep, but its basically identical to the info in the logs when its  
restarting itself. I have upgraded to MySQL 5.5 as of yesterday, so  
the error info differs due to the version now. Here is the log output:


110909 17:27:35 mysqld_safe Starting mysqld daemon with databases from  
/var/db/mysql

110909 17:27:35 InnoDB: The InnoDB memory heap is disabled
110909 17:27:35 InnoDB: Mutexes and rw_locks use GCC atomic builtins
110909 17:27:35 InnoDB: Compressed tables use zlib 1.2.3
110909 17:27:35 InnoDB: Initializing buffer pool, size = 2.0G
110909 17:27:36 InnoDB: Completed initialization of buffer pool
110909 17:27:36 InnoDB: highest supported file format is Barracuda.
110909 17:27:36  InnoDB: Waiting for the background threads to start
110909 17:27:37 InnoDB: 1.1.8 started; log sequence number 1589339
110909 17:27:37 [Note] Slave SQL thread initialized, starting  
replication in log 'mysql-bin.002830' at position 293541, relay log  
'./tau-relay-bin.000920' position: 253

110909 17:27:37 [Note] Event Scheduler: Loaded 0 events
110909 17:27:37 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.5.15'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110909 17:27:37 [Note] Slave I/O thread: connected to master  
'slave@kappa:3306',replication started in log 'mysql-bin.002830' at  
position 293541


Just not giving any hit of a problem

thanks Andy.

Quoting Suresh Kuna :


can you remove it from service and start it normally using mysqld_safe with
log warnings enabled in the cnf file.

On Fri, Sep 9, 2011 at 4:16 PM,  wrote:


Hi,

 that really is the complete error log, that exact same info gets repeated
over and over, there is zero in the syslog and I get this behaviour when
running with no my.cnf (I do obviously have one but I tried without and it I
still see the prob, so that probably makes things easier from a
troubleshooting perspective)...
The system has loads of free RAM (8GB total).
Really the system isn't giving me much to go in in terms of clues

Andy.






--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Binary builds for AIX

[Peter Gershkovich]

I noticed that there is no binary builds for AIX any more. 
What would be the best way to install a current version of MySQL (5.5)  on AIX?
Specifically I am looking for instructions for AIX 6.1 and/or 7.1 
Thanks,
Peter

 
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: MySQL daemons restarting every 7 minutes

[Suresh Kuna]

can you remove it from service and start it normally using mysqld_safe with
log warnings enabled in the cnf file.

On Fri, Sep 9, 2011 at 4:16 PM,  wrote:

> Hi,
>
>  that really is the complete error log, that exact same info gets repeated
> over and over, there is zero in the syslog and I get this behaviour when
> running with no my.cnf (I do obviously have one but I tried without and it I
> still see the prob, so that probably makes things easier from a
> troubleshooting perspective)...
> The system has loads of free RAM (8GB total).
> Really the system isn't giving me much to go in in terms of clues
>
> Andy.
>
>
> Quoting Suresh Kuna :
>
>  Can yo paste the complete error log, Ram memory size and configuration
>> file
>> here and make sure the machine has enough memory to run the services.
>>
>> Check the sys log for what is happening just before the service restart.
>>
>>
>
>
>


-- 
Thanks
Suresh Kuna
MySQL DBA

Re: strange mysql update ..

[Derek Downey]

Try searching for a row that has a login_date of '-00-00 00:00:00'

- Derek

On Sep 9, 2011, at 8:52 AM, umapathi b wrote:

> Any update from anybody ?
> 
> 
> -- Forwarded message --
> From: umapathi b 
> Date: Thu, Sep 8, 2011 at 4:28 AM
> Subject: Re: strange mysql update ..
> To: Ananda Kumar 
> Cc: mysql@lists.mysql.com
> 
> 
> Here is the o/p after the update ..
> 
> 
>   user_id: 16078845
>   drivers_license: TEST1140DL
>login_date: 2011-06-19 11:20:07
> course_id: 1011
>  regulator_id: 10840
> test_info: 
>   completion_date: 2011-06-19 11:37:16
>print_date: NULL
>  password: test1140dl
> certificate_number: NULL
> login: test114...@1140dl.com
> 
> 
> - Umapathi
> 
> 
> On Thu, Sep 8, 2011 at 4:23 AM, Ananda Kumar  wrote:
> 
>> Can you lets us know what is the output of
>> 
>> select * from user_info where user_id=16078845;
>> 
>> 
>> On Thu, Sep 8, 2011 at 1:02 PM, umapathi b  wrote:
>> 
>>> I wanted to change the login_date of one user . The original data of that
>>> user is like this ..
>>> 
>>> select * from user_info where user_id = 16078845 \G
>>> *** 1. row ***
>>>  user_id: 16078845
>>>  drivers_license: TEST1140DL
>>>   login_date: 2011-06-19 11:20:07
>>>course_id: 1011
>>> regulator_id: 10840
>>>test_info: 
>>>  completion_date: 2011-06-19 11:37:16
>>>   print_date: NULL
>>> password: test1140dl
>>> certificate_number: NULL
>>>login: test114...@1140dl.com
>>> 
>>> I fired the update statement in a wrong way ..like this ..
>>> 
>>> update user_info set login_date='2011-08-05 04:15:05' and user_id
>>> =16078845
>>> limit 1 ;
>>> ( I forgot to use where . instead of where I used and )
>>> update user_info set login_date='2011-08-05 04:15:05' where user_id
>>> =16078845 limit 1 ; ( this is the query intended )
>>> 
>>> after the update ..I got this message ..
>>> mysql> update user_info set login_date='2011-08-05 04:15:05' and user_id
>>> =16078845 limit 1;
>>> Query OK, 1 row affected, 1 warning (0.02 sec)
>>> Rows matched: 1  Changed: 1  Warnings: 0
>>> 
>>> It shows that one record is affected and one row changed ..
>>> I did show warnings ..the output is like this ..
>>> 
>>> mysql> show warnings;
>>> 
>>> +-+--+-+
>>> | Level   | Code | Message
>>> |
>>> 
>>> +-+--+-+
>>> | Warning | 1292 | Truncated incorrect DOUBLE value: '2011-08-05 04:15:05'
>>> |
>>> 
>>> 
>>> +-+--+-+
>>> 
>>> But I could not get any record in the table with the updated login_date ..
>>> mysql> select * from user_info where login_date like '2011-08-05%' ;
>>> Empty set (0.67 sec)
>>> 
>>> So my question is what happened exactly ?
>>> Why no records updated ?
>>> 
>>> Help is highly appreciated in this regard ..
>>> 
>>> - Umapathi
>>> umapath...@gmail.com
>>> 
>> 
>> 


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Fwd: strange mysql update ..

[umapathi b]

Any update from anybody ?


-- Forwarded message --
From: umapathi b 
Date: Thu, Sep 8, 2011 at 4:28 AM
Subject: Re: strange mysql update ..
To: Ananda Kumar 
Cc: mysql@lists.mysql.com


Here is the o/p after the update ..


   user_id: 16078845
   drivers_license: TEST1140DL
login_date: 2011-06-19 11:20:07
 course_id: 1011
  regulator_id: 10840
 test_info: 
   completion_date: 2011-06-19 11:37:16
print_date: NULL
  password: test1140dl
certificate_number: NULL
 login: test114...@1140dl.com


- Umapathi


On Thu, Sep 8, 2011 at 4:23 AM, Ananda Kumar  wrote:

> Can you lets us know what is the output of
>
> select * from user_info where user_id=16078845;
>
>
> On Thu, Sep 8, 2011 at 1:02 PM, umapathi b  wrote:
>
>> I wanted to change the login_date of one user . The original data of that
>> user is like this ..
>>
>> select * from user_info where user_id = 16078845 \G
>> *** 1. row ***
>>   user_id: 16078845
>>   drivers_license: TEST1140DL
>>login_date: 2011-06-19 11:20:07
>> course_id: 1011
>>  regulator_id: 10840
>> test_info: 
>>   completion_date: 2011-06-19 11:37:16
>>print_date: NULL
>>  password: test1140dl
>> certificate_number: NULL
>> login: test114...@1140dl.com
>>
>> I fired the update statement in a wrong way ..like this ..
>>
>> update user_info set login_date='2011-08-05 04:15:05' and user_id
>> =16078845
>> limit 1 ;
>> ( I forgot to use where . instead of where I used and )
>> update user_info set login_date='2011-08-05 04:15:05' where user_id
>> =16078845 limit 1 ; ( this is the query intended )
>>
>> after the update ..I got this message ..
>> mysql> update user_info set login_date='2011-08-05 04:15:05' and user_id
>> =16078845 limit 1;
>> Query OK, 1 row affected, 1 warning (0.02 sec)
>> Rows matched: 1  Changed: 1  Warnings: 0
>>
>> It shows that one record is affected and one row changed ..
>> I did show warnings ..the output is like this ..
>>
>> mysql> show warnings;
>>
>> +-+--+-+
>> | Level   | Code | Message
>> |
>>
>> +-+--+-+
>> | Warning | 1292 | Truncated incorrect DOUBLE value: '2011-08-05 04:15:05'
>> |
>>
>>
>> +-+--+-+
>>
>> But I could not get any record in the table with the updated login_date ..
>> mysql> select * from user_info where login_date like '2011-08-05%' ;
>> Empty set (0.67 sec)
>>
>> So my question is what happened exactly ?
>> Why no records updated ?
>>
>> Help is highly appreciated in this regard ..
>>
>> - Umapathi
>> umapath...@gmail.com
>>
>
>

Technofloor

[Technofloor]

/*--Text Styles--*/
.ws6 {font-size: 8px;}
.ws7 {font-size: 9.3px;}
.ws8 {font-size: 11px;}
.ws9 {font-size: 12px;}
.ws10 {font-size: 13px;}
.ws11 {font-size: 15px;}
.ws12 {font-size: 16px;}
.ws14 {font-size: 19px;}
.ws16 {font-size: 21px;}
.ws18 {font-size: 24px;}
.ws20 {font-size: 27px;}
.ws22 {font-size: 29px;}
.ws24 {font-size: 32px;}
.ws26 {font-size: 35px;}
.ws28 {font-size: 37px;}
.ws36 {font-size: 48px;}
.ws48 {font-size: 64px;}
.ws72 {font-size: 96px;}
.wpmd {font-size: 13px;font-family: Arial,Helvetica,Sans-Serif;font-style: normal;font-weight: normal;}
/*--Para Styles--*/
DIV,UL,OL /* Left */
{
 margin-top: 0px;
 margin-bottom: 0px;
}

Re: MySQL daemons restarting every 7 minutes

[a . smith]

Hi,

  that really is the complete error log, that exact same info gets  
repeated over and over, there is zero in the syslog and I get this  
behaviour when running with no my.cnf (I do obviously have one but I  
tried without and it I still see the prob, so that probably makes  
things easier from a troubleshooting perspective)...

The system has loads of free RAM (8GB total).
Really the system isn't giving me much to go in in terms of clues

Andy.

Quoting Suresh Kuna :


Can yo paste the complete error log, Ram memory size and configuration file
here and make sure the machine has enough memory to run the services.

Check the sys log for what is happening just before the service restart.






--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: running a duplicate database

[Rik Wasmus]

> Am 09.09.2011 11:09, schrieb Dave Dyer:
> > Is there a halfway house between a single database and a full
> > master-slave setup?
> > 
> > I have a database with one "piggish" table, and I'd like to direct
> > queries that search the pig to a duplicate database, where it won't
> > affect all the routine traffic.
> > 
> > I could definitely do this by setting up a slave server, but for my
> > purposes it would be just as effective, and lots easier, if mysql could
> > automatically maintain a duplicate of the database.  Presumably this
> > would work internally like an internal auto-slave, with a binary log of
> > changes to the master database self-consumed to maintain the duplicate.
> > 
> > As a bonus, I could backup the duplicate instead of the master, so that
> > won't affect the routine traffic either.
> 
> you can run as many slaves on the same machine as you want by
> using a different port for all instances and stop/backup/start
> one of them per script - doing this since years

No problem indeed.

> it makes no sense "maintain a duplicate of the database"for backups
> becasue mysqld have to be stooped for effective rsync-backups which
> are much faster as dumps and here are we again at the point using
> a slave on a different port

I concur that dumps are not an effective way of backup, they take ages when 
any decent size database.  We have had great experiences with Percona's 
Xtrabackup (http://www.percona.com/docs/wiki/percona-xtrabackup:start) for 
hotcopies, which also work with InnoDB. But on a heavily used db-server, it 
DOES make sense to run the backup on a (unused) slave, there's still some 
overhead & locking involved, and if your DB is running hot 24/7 you don't want 
that one to do anything that can be done somewhere else.
-- 
Rik Wasmus

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: running a duplicate database

[Reindl Harald]

Am 09.09.2011 11:09, schrieb Dave Dyer:
> Is there a halfway house between a single database and a full master-slave 
> setup?
>
> I have a database with one "piggish" table, and I'd like to direct queries 
> that search the pig to a duplicate database, where it won't affect all the 
> routine traffic.  
>
> I could definitely do this by setting up a slave server, but for my purposes 
> it would be just as effective, and lots easier, if mysql could automatically 
> maintain a duplicate of the database.  Presumably this would work internally 
> like an internal auto-slave, with a binary log of changes to the master 
> database self-consumed to maintain the duplicate.
>
> As a bonus, I could backup the duplicate instead of the master, so that won't 
> affect the routine traffic either.

you can run as many slaves on the same machine as you want by
using a different port for all instances and stop/backup/start
one of them per script - doing this since years

it makes no sense "maintain a duplicate of the database"for backups
becasue mysqld have to be stooped for effective rsync-backups which
are much faster as dumps and here are we again at the point using
a slave on a different port



signature.asc
Description: OpenPGP digital signature

running a duplicate database

[Dave Dyer]

Is there a halfway house between a single database and a full master-slave 
setup?

I have a database with one "piggish" table, and I'd like to direct queries that 
search the pig to a duplicate database, where it won't affect all the routine 
traffic.  

I could definitely do this by setting up a slave server, but for my purposes it 
would be just as effective, and lots easier, if mysql could automatically 
maintain a duplicate of the database.  Presumably this would work internally 
like an internal auto-slave, with a binary log of changes to the master 
database self-consumed to maintain the duplicate.

As a bonus, I could backup the duplicate instead of the master, so that won't 
affect the routine traffic either.


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org