Just wondering what they are. I'd rather not use the MySQL root user for a
backup script, if I can get away with MySQL user with reduced privileges, for
the following command:
mysqlcheck -ao --auto-repair --all-databases -u someuserotherthanroot -pPASSWORD
...Rene
--
MySQL General Mailing Li
I am trying top run these 2 SELECT queries using mysql_real_query in MySQL-C.
The only difference between them is changing the first hex value from 41 to 01.
It if is 41, the query runs fine. When I change it to 01 I get the following
segmentation fault.
segfault at 0 ip 00402be6 sp 00
>> I would never have any confidence that the replication
>> is solid enough to use the slave server for backup purposes.
> I agree completely there. That's the other reason I like filesystem
> snapshots is that it allows you to take a backup from
> the master relatively painlessly.
I've thou
> I would never have any confidence that the replication is solid
> enough to use the slave server for backup purposes.
I agree completely there. That's the other reason I like filesystem snapshots
is that it allows you to take a backup from the master relatively painlessly.
-Original Messa
> I would say that it's very important to know why data
> is getting out of sync between your master and slave.
Ultimately, I agree. But since it's a canned application, getting to
that point might be hard, and once it is resolved, new issues might
arise. I would never have any confidence that t
On 12/4/09 3:14 PM, "Gavin Towey" wrote:
> I would say that it's very important to know why data is getting out of sync
> between your master and slave. Fixing those root causes would eliminate the
> need for this.
i very much agree. the only instances of slaves getting out of whack that
i've e
I think he's trying to say that this method wouldn't work for innodb, unless
you copied files from an LVM snapshot, or something similar.
I would say that it's very important to know why data is getting out of sync
between your master and slave. Fixing those root causes would eliminate the
nee
On 12/4/09 11:59 AM, "Robinson, Eric" wrote:
>> (2) why delete slave logs when you can
>> restart the slave with --skip-slave and
>> then use CHANGE MASTER TO?
>
> Well... I guess mainly because I didn't know about that option! I
> thought I needed to "fake out" mysql on this, but it sounds like
> (1) innodb?
It's an off-the-shelf application that uses MyISAM tables. It is
possible to convert to innodb, but I have not been sold on innodb in
terms of its performance characteristics for this particular
application. Maybe I've been reading the wrong stuff. Do you have
general thoughts on t
i have two questions. (1) innodb? (2) why delete slave logs when you can
restart the slave with --skip-slave and then use CHANGE MASTER TO?
tom
On 12/4/09 6:34 AM, "Robinson, Eric" wrote:
>
> Let's face it, sometimes the master and slave get out of sync, even when
> 'show slave status' and 's
Let's face it, sometimes the master and slave get out of sync, even when
'show slave status' and 'show master status' indicate that all is well.
And sometimes it is not feasible to wait until after production hours to
resync them. We've been working on a method to do an emergency
hot-resync durin
11 matches
Mail list logo
