Got a very strange situation, where I receive two similar DELETE
statement in the same binary log position, due to which replication slave
is stopped due to following error:
Could not execute DELETE rows event on table db1.xyz.; Can't find record in
'xyz' , error code:1032.
ecoming a
> problem and thus we had to move to another directory.
> - setting that was changed is : log_bin =
> - old binary logs were moved to the new directory after shutting down
> the database
> - database started up and continued as normal, however stop
pire_logs_days.
5.0 -- I don't think anything relevant has changed during 4.0 thru 5.6.
> -Original Message-
> From: Machiel Richards - Gmail [mailto:machiel.richa...@gmail.com]
> Sent: Wednesday, July 03, 2013 3:20 AM
> To: mysql list
> Subject: Master not creating n
.
- setting that was changed is : log_bin =
- old binary logs were moved to the new directory after shutting
down the database
- database started up and continued as normal, however stopped at
the last binary log when it filled up and complained about a corrupted
binary log
.
However, the moment the file reached the file size of 100Mb, it
does not go on to create a new binlog file called mysql-bin.2 and the
replication fails stating that it is unable to read the binary log file.
Thus far we have done a flush logs and reset master , but the
same
may indicate a
brief delay.
> -Original Message-
> From: Mihamina Rakotomandimby [mailto:miham...@rktmb.org]
> Sent: Monday, June 17, 2013 5:35 AM
> To: mysql@lists.mysql.com
> Subject: Re: SLAVE aware of binary log file switch?
>
> On 2013-06-17 14:43, Denis Jedig w
On 2013-06-17 14:43, Denis Jedig wrote:
Say the binary log file (on the master) has reached its maximum
size, so that it has to switch to a "+1" binary log file: does he
inform the SLAVE of that switch so that the SLAVE updates its
information about the MASTER status?
The master does n
Hi all,
Given a MASTER and a SLAVE.
When launching the SLAVE, it knows about the binary log file used by the
MASTER and the position in that log file.
Say the binary log file (on the master) has reached its maximum size, so
that it has to switch to a "+1" binary log file: does he
Am 17.06.2013 13:11, schrieb Mihamina Rakotomandimby:
Say the binary log file (on the master) has reached its maximum
size, so that it has to switch to a "+1" binary log file: does he
inform the SLAVE of that switch so that the SLAVE updates its
information about the MASTER status?
(): 'Found invalid
event in binary log', data_len: 100, event_type: 2
100111 16:16:51 [ERROR] Error in Log_event::read_log_event(): 'Found invalid
event in binary log', data_len: 100, event_type: 2
100111 16:17:08 [ERROR] Error in Log_event::read_log_event(): 'Found inv
All
Lately I am struggling with big tables maintenance,
I've just made a very quick and dirty tool for having summaries from the
binary log files,
like how many times a table was updated, or inserted or deleted.
Before going any further I would really appreciate your opinion to know if
All
Lately I am struggling with big tables maintenance,
I've just made a very quick and dirty tool for having summaries from the
binary log files,
like how many times a table was updated, or inserted or deleted.
Before going any further I would really appreciate your opinion to know if
logs except the last one
[/Incremental]
[Schedule]
Day 1: execute incremtal
..
Day 7: execute incremtal
execute full, binary log index is reset
[/Schedule]
Please tell me if this is the best & correct way to do it, and if any of my
following statements are incorrect/I have missed somet
Guys,
I would like to know if there is a way to have individual databases
under the same instance or server write to separate binary log
files. The idea is to have multiple binary log file for each
database on the same server. The problem that I experiencing is
sorting through the binary
a full mysqldump with --flush-logs --master-data=2
>>> - do a bunch of stuff that writes data
>>> - drop the database, and recreate it, flushing the log
>>> - make a copy of the binary log made since the mysqldump
>>> - import the mysqldump I made locally
>
data=2
> > - do a bunch of stuff that writes data
> > - drop the database, and recreate it, flushing the log
> > - make a copy of the binary log made since the mysqldump
> > - import the mysqldump I made locally
> > => now I have all data correctly restored up t
- Import a full mysqldump file from the prodution db
> - flush logs
> - run a full mysqldump with --flush-logs --master-data=2
> - do a bunch of stuff that writes data
> - drop the database, and recreate it, flushing the log
> - make a copy of the binary log made since the mys
ter-data=2
- do a bunch of stuff that writes data
- drop the database, and recreate it, flushing the log
- make a copy of the binary log made since the mysqldump
- import the mysqldump I made locally
=> now I have all data correctly restored up to that point
Now, I attempt to restore the
Hi Guys,
Need some pointers. I've got a MySQL server (5.0.22) which is basically
pulling data from SQL Server into a file and then I'm using mysqlimport
to load the data into the DB.
The updates are being generated like every 2 to 5 seconds.
Due to this, my Binary Log files are huge!
aster A
are replicated to slave A, and inserts on master B are replicated to slave
B). However, queries that are run on master A, do *not* make it all the
way to slave B. The queries execute on master B but I have verified that
they are not being written to master B's binary log. Hence, slave
> > On Wed, 05 Apr 2006 08:44:52 -0300
> > Mauricio Pellegrini <[EMAIL PROTECTED]> wrote:
> >
> > > Hi ,
> > >
> > > Yesterday our main database was dropped by mystake.
> > > This has never happened before.
> > >
> >
> >
> > Yesterday our main database was dropped by mystake.
> > This has never happened before.
> >
> > Furtunately we had a daily backup performed with mysqldump at about
> > 06:00 am that day.
> >
> > As the problem ocurred at about 12:00am we had to
ase was dropped by mystake.
> This has never happened before.
>
> Furtunately we had a daily backup performed with mysqldump at about
> 06:00 am that day.
>
> As the problem ocurred at about 12:00am we had to restore the
> transactions from the binary log ( we have sev
Hi ,
Yesterday our main database was dropped by mystake.
This has never happened before.
Furtunately we had a daily backup performed with mysqldump at about
06:00 am that day.
As the problem ocurred at about 12:00am we had to restore the
transactions from the binary log ( we have several
Yes, look at the PURGE LOGS command.
Rithish Saralaya wrote:
> Hello.
>
> Can I delete off the binary log files manually? I do not want
> to 'RESET MASTER', as it will clear all the binary logs, and
> that's not what I want to do. The database is backed up every
&
Hello.
Can I delete off the binary log files manually? I do not want to 'RESET
MASTER', as it will clear all the binary logs, and that's not what I want to
do. The database is backed up every midnight, and I wouldn't want to keep
any of the bin logs except the latest one.
We
In answer to my own question:
Why don't the binary logs write?
The '%-bin.index' file left over from previous version (4.1.9) had to be
deleted after the conversion to 5.1.6.
By deleting this file, the binary logs started to recreate.
I hope this is useful to somebody :)
Ben
Ben Clewett
Dear MySQL,
I have just upgraded 4.1.9 to 5.1.6, by compiling source code. I have
lost my binary logs.
http://dev.mysql.com/doc/refman/5.0/en/binary-log.html
eg: my-bin.01
my-bin.02
The usual option is present:
[mysqld]
log-bin = /usr/local/mysql/logs/my-bin
**or**
[mysqld]
l
log, binary update log, and slow queries
> log, whatever log has been activated)". But apparently it isn't.
>
> I was hoping that there was a way to get that information in the binary
> log, but it appears more likely the documentation is wrong.
>
>
I realize that.
The documentation states that username and timestamp,
by default, are logged to "(update log, binary update log, and slow queries
log, whatever log has been activated)". But apparently it isn't.
I was hoping that there was a way to get that information in the b
Hello.
I think these lines from sql/mysqld.cc from 4.1.13 distribution shows
that --log-long-format doesn't affect the behavior of MySQL:
{"log-long-format", '0',
"Log some extra information to update log. Please note that this
option is deprecated; see --log-short-format option.",
0, 0,
The current documentation states :
Log some extra information to the log files (update log, binary update
log, and slow queries log, whatever log has been activated). For example,
username and timestamp are logged for queries. Before MySQL 4.1, if you
are using --log-slow-queries and --log-l
Hi,
is there any setting in binary log that helps me to create a log for a
specific table in a database? I know that I can force binary log to create
a log for a specific database, but I need it for a specific table.
thanks
--
MySQL General Mailing List
For list archives: http
I found the solution to my own problem...
the log-bin option is a specific filename. so when you set:
log-bin=/logging
mysql must have ownership of the / folder, as it is trying to create /logging.001 and
/logging.index
easily fixed by adding the file-name to the path...
log-bin=/logging/h
I'm trying to move my binary log files onto a different drive than our main data drive
to get a little performance boost.
the drives are set up like so:
drive 1 (sda):
swap
/boot
/usr
drive 2 (sdb):
/
mysql is installed in /usr/local/mysql and its data directory is /usr/local/mysql/
I am using MySQL 4.1.3 and wondering if there is any way to get binary log, and
general log location by querying database.
I've checked
mysql> show variables;
command, but it only returns if log is ON or OFF.
Thanks,
Aleksandar
Hi,
I have enabled the binary log on MySQL (4.0.20). The name of the binary
log is hostname-bin.001, hostname-bin.002, etc ...
What will happen if the suffix become 999? Will error occurs when flush
logs is executed?
Regards,
Michael
re both showing a status of I/O thread not running.
> In the mysqld.log file for both slaves I found the following entry:
>
> 040628 12:59:08 Error reading packet from server: bogus data in log event
> (server_errno=1236)
> 040628 12:59:08 Got fatal error 1236: 'bogus data
12:59:08 Error reading packet from server: bogus data in log event
(server_errno=1236)
040628 12:59:08 Got fatal error 1236: 'bogus data in log event' from master when
reading data from binary log
040628 12:59:08 Slave I/O thread exiting, read up to log 'daredevil1-bin.001',
p
I get this error on the slave:
040614 10:19:07 Error reading packet from server: bogus data in log
event (server_errno=1236)
040614 10:19:07 Got fatal error 1236: 'bogus data in log event' from
master when reading data from binary log
040614 10:19:07 Slave I/O thread exiting, read
Hi I am using replication to do online backups for my tables. Now my next
task is to automate cleaning up of binary log files from Master server.
Assuming I have more than one slave running, and may be at the time of
clean up one of the slave is down for backup, how can I be sure that my
clean up
On 23 Mar 2004, at 10:38, [EMAIL PROTECTED] wrote:
Hello colleagues, I'd like to know
IF by enabling the binary logs production I'll affect meaningfully the
MySQL DB performances, and
HOW MUCH the performances are impacted
I just tested a load of a 6GB mysqldump (MyISAM tables), on an unloaded
H
Hello colleagues, I'd like to know
IF by enabling the binary logs production I'll affect meaningfully the
MySQL DB performances, and
HOW MUCH the performances are impacted
Any witnesses on this topic?
Regards
Enrico
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To
On Mon, Jan 05, 2004 at 09:12:24AM +1300, Sam Vilain wrote:
> No-one out there doing step-by-step replay of binary logs ?
mysqlbinlog
--
Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo!
<[EMAIL PROTECTED]> | http://jeremy.zawodny.com/
MySQL 4.0.15-Yahoo-SMP: up 162 days, proce
George Mathew <[EMAIL PROTECTED]> wrote:
> Seems to be the binary log saves all INSERT statements, even if it is
> a duplicate error.
Only successfully executed INSERTs are written to the binary logs.
> How could I restore my table using mysqlbinlog if there
> are duplicat
Seems to be the binary log saves all INSERT statements, even if it is
a duplicate error. How could I restore my table using mysqlbinlog if
there
are duplicates in the log file.
Please help
Thanks,
George Mathew.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
I would greatly appreciate your notes if you are willing to post them. I'm currently
preparing for the core exam.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
No-one out there doing step-by-step replay of binary logs ?
On Tue, 30 Dec 2003 17:52, Sam Vilain wrote;
> Hi there,
>
> Is there a utility out there to do transaction-at-a-time view and/or
> replay with MySQL's binary log ? Primarily for audit / debug
> purpose
Hi there,
Is there a utility out there to do transaction-at-a-time view and/or
replay with MySQL's binary log ? Primarily for audit / debug
purposes.
I'm only interested in using it with the proper database back-end, not
ISAM.
--
Sam Vilain, [EMAIL PROTECTED]
In married life
On Tue, 9 Dec 2003, Mayuran Yogarajah wrote:
> Diana Soares wrote:
>
> >Use "PURGE {MASTER|BINARY} LOGS TO 'log_name'" instead of "RESET
> >MASTER".
> >>From the manual:
> >
> >"
> >Deletes all the binary logs listed in the log index that are strictly
> >prior to the specified log or date. The log
Diana Soares wrote:
Use "PURGE {MASTER|BINARY} LOGS TO 'log_name'" instead of "RESET
MASTER".
From the manual:
"
Deletes all the binary logs listed in the log index that are strictly
prior to the specified log or date. The logs also are removed from this
list recorded in the log index file, so tha
and have replication
> setup in the following manner: There are two machines (m1 and m2).
> Replication is setup in a circular way. Both machines are master and
> slave, more specifically, m1 is master to m2 and m2 is master to m1.
> I checked today and saw that one of the machines
one of the machines had a bunch of
binary log files (see below). I read in the MySQL documentation that
you can delete the logs by issuing a RESET MASTER command. I am
wonder how this will affect replication. Is this going to break replication
in any way? Is it safe to simply delete the binary
I've been trying to understand the format of the MySQL binary logs: I've
noted from /clients/log_event.h that there are two formats, the "old"
one with an event header length of 13 bytes, and a "new" one with an
event header length of 19 bytes. That's perfectly clear: but supposing I
have two logs,
I'm trying to write a script to weekly remove MySQL logs, the general,
error and binary log files.
Following the MySQL documentation, I've written a script that moves all
current log files, then executes mysqladmin flush-logs.
My question is this on the binary logs (bin.001, bi
r issue, and I'm not sure
> how
> to deal with it. I've scoured the manual, searched list archives, the
> web, etc., and am coming up empty.
>
> Somehow, the server is recording the Binary log in the data directory.
> Each of these log files takes up a gigabyte. This
ql
--pid-file=/var/lib/mysql/inferno.pid --skip-locking
We're running version 3.23.41 for pc-linux-gnu on i686, running on SuSE
Linux 7.1, kernel 2.4.18 #2 SMP on a Dual-Processor Pentium II 450MHz
server
So, if any of you can shed some light as to why it would be saving the
binary log agains
hello,
i am a MySQL newbie, my MySQL server is 3.23.36 install on RH7.1.
i am trying to enable a binary log in my server recently, i give a command:
'safe_mysqld --log-bin' to enable it, but i think it doesn't work,
because i cann't find any files such as 'hostna
On Wed, Jun 11, 2003 at 03:30:01PM -0500, Sam Jumper wrote:
> Is it possible to have more than one binary log per master or is it
> possible to start more than one thread to execute queries?
>
> I have 2 computers in a master and slave configuration. The slave is
> running wi
: Wednesday 11 June 2003 21:30
To: [EMAIL PROTECTED]
Subject: binary log
Is it possible to have more than one binary log per master or is it possible
to start more than one thread to execute queries?
I have 2 computers in a master and slave configuration. The slave is
running without error
Is it possible to have more than one binary log per master or is it
possible to start more than one thread to execute queries?
I have 2 computers in a master and slave configuration. The slave is
running without error but it can't keep up with the volume of updates
being performed o
The manual does not give any warnings about using "load data local" when
applying changes via the binary log.
I am having trouble getting my head around how this would work.
IE if you update a table via "load data local" then how can you replicate
these changes using the
I'm trying to setup binary logging to eventually get replication
between two servers. However, any updates that I do to the
database are never written to the binary log.
I'd appreciate any pointers to what I may have misconfigured. Here
are some details about what I've tried s
Hello,
I use MySQL in a production environment where it is running a few
databases. I make hourly db backups using the perl hot copy script
distributed with MySQL. I would like to be able to restore my db down
to the minute with the binary log, but the options to the binary log
parser are
file.
Is this what you meant.
Thanks
sam
- Original Message -
From: "gerald_clark" <[EMAIL PROTECTED]>
To: "sam" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, January 31, 2003 2:40 PM
Subject: Re: binary log not recording 4.0.9
> Y
s.
I appreciate any help you can offer,
Sam Pizzuto
- Original Message -
From: "gerald_clark" <[EMAIL PROTECTED]>
To: "sam" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, January 31, 2003 9:20 AM
Subject: Re: binary log not recording 4
If your application is opening one database, and then updating
medic.sometable, the update will not be recorded in the bin file.
sam wrote:
I am trying to use replication with 4.0.9.
Changes to the datbase are not being recorded in
the bin file on the master for a DB called Medic
when present
I am trying to use replication with 4.0.9.
Changes to the datbase are not being recorded in
the bin file on the master for a DB called Medic
when presented by an application but will if I
setup a test table in the DB mysql and use the
mysql client to insert/update.
At this point I have no idea
At 16:21 -0500 12/11/02, David Nedved wrote:
Hi All,
I have two qestions about the binary log files that I couldn't find the
answer to.
1.) how do you force a log switch other than startup / shutdown?
FLUSH LOGS
2.) when the number gets to 999 does it keep going with more digits,
Hi All,
I have two qestions about the binary log files that I couldn't find the
answer to.
1.) how do you force a log switch other than startup / shutdown?
2.) when the number gets to 999 does it keep going with more digits, wrap around, or
some other behavior?
I'm running mysql-ma
In 3.23.x versions of MySQL the actual binary log file sizes stayed
fairly consistent. An 'empty' log file for instance on 3.23.53a is 73
bytes. I have a situation where I'm doing a roll-your-own replication
from many sites to one central server where the remote sites are on
everyth
021009 12:56:49 mysqld started
/usr/sbin/mysqld: ready for connections
021009 12:56:49 Slave: connected to master '[EMAIL PROTECTED]:3306',
replication started in log 'FIRST' at position 4
021009 12:56:49 Error reading packet from server: Binary log is not open
(read_errno
Apologies to the list. Apparently the question I asked regarding binary
data dumps is an issue involving a MySQL startup parameter: log-bin.
Apparently this is the redo-log facility of MySQL for all successful
updates. This can be turned on or off. Question answered.
Thanks,
Rob
Robert Fox
S
>Description:
If an update is made to a master using the syntax
'INSERT INTO database.table' etc... on a mysql connection
where no 'USE database' command has been given then the updates
are written to the master binary log correctly, and u
to mysql-bin.61679pos=4
># at 46
>#020626 9:58:04 server id 2 Stop
>
>
>
>See - it's REALLY frequent..
>
>
>*shrug* who knows ... Anyone?? ;)
>
>G
>
>
>
>On Tue, 25 Jun 2002, Paul DuBois wrote:
>
>> At 16:31 +0200 6/25/02
otate to mysql-bin.61679pos=4
# at 46
#020626 9:58:04 server id 2 Stop
See - it's REALLY frequent..
*shrug* who knows ... Anyone?? ;)
G
On Tue, 25 Jun 2002, Paul DuBois wrote:
> At 16:31 +0200 6/25/02, Gary Colman wrote:
> >Hi
> >
> >Every few seconds, my mysq
At 16:31 +0200 6/25/02, Gary Colman wrote:
>Hi
>
>Every few seconds, my mysql server generates a new binary log file
>with an incremented id number "${hostname}-bin.x"
>According to the logs, this should happen only when a reload or flush
>type command is issued ..
Hi
Every few seconds, my mysql server generates a new binary log file
with an incremented id number "${hostname}-bin.x"
According to the logs, this should happen only when a reload or flush
type command is issued ...
mysql variables:
flush off
log_bin on
max_b
...
http://www.mysql.com/doc/O/p/Option_files.html
-Original Message-
From: Scalper [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 03, 2002 7:10 AM
To: [EMAIL PROTECTED]
Subject: Binary Log and WinXP Services
I am running Windows XP with MySQL running as a service. When I want to
I am running Windows XP with MySQL running as a service. When I want to
run MySQL with the option for logging (--log -bin), I have to start the
service MANUALLY and type the --log -bin in the parameters box each time I
restart the server. Is there an easier way to do this?
Thx,
Craig
I am reading the documentation about the binary log, in particular
binlog-do-db=database_name
binlog-ignore-db=database_name
(a) Can these be specified in the my.cnf file?
(b) Can multiple databases be specified, either as a list or via multiple entries in
the
configuration?
We're ru
are
not written to the binary log. I perfectly understand this if
I have one server. But assume I have a master server, and a
slave server that replicates the master. Let's say I distribute reads.
Let's say I issue the following queries on the master (I use
BEGIN and COMMIT for consisten
are
not written to the binary log. I perfectly understand this if
I have one server. But assume I have a master server, and a
slave server that replicates the master. Let's say I distribute reads.
Let's say I issue the following queries on the master (I use
BEGIN and COMMIT for consisten
Hi!
> "Heikki" == Heikki Tuuri <[EMAIL PROTECTED]> writes:
Heikki> Guilhem,
Heikki> this is a known problem and mentioned in the Restrictions section of the
Heikki> InnoDB online manual.
Heikki> It is not the correct way to run SQL statements in the autocommit mode on
Heikki> the slave ser
Hi!
> "Heikki" == Heikki Tuuri <[EMAIL PROTECTED]> writes:
Heikki> Guilhem,
Heikki> this is a known problem and mentioned in the Restrictions section of the
Heikki> InnoDB online manual.
Heikki> It is not the correct way to run SQL statements in the autocommit mode on
Heikki> the slave ser
are
not written to the binary log. I perfectly understand this if
I have one server. But assume I have a master server, and a
slave server that replicates the master. Let's say I distribute reads.
Let's say I issue the following queries on the master (I use
BEGIN and COMMIT for consisten
Hello there,
I use MySQL (4.0.1) with InnoDB tables with binary logging on.
I see that the
BEGIN and COMMIT statements that wrap my queries are
not written to the binary log. I perfectly understand this if
I have one server. But assume I have a master server, and a
slave server that
This is my second time posting this question to the mailing list. I
received no responses the first time I posted this.
In the MySQL documentation, it states that the binary log will be replacing
the update log, and it should be used in its place as it can do anything
the update log can. I&#
licate-ignore-table=GPW.c
replicate-ignore-table=GPW.b
replicate-ignore-table=GPW.d
replicate-ignore-table=GPW.e
server-id=4
log-bin
We are frequently receiving errors in binary log which effect in
replication failure:
011017 0:48:50 Slave: did not get the expected error running query from
In the MySQL documentation, it states that the binary log will be replacing
the update log, and it should be used in its place as it can do anything
the update log can. I'm not sure this is the case. The update log shows
where the individual connections connect from and what user connect
hi,
i have a lamer question:
where is my binary log file? i can't find it.
i am sure it exists because grows crazy, when
i restore a database from dumpfile.
i found nothing about binary log in my.cnf.
version: mysql 3.23.32-log
install path: /usr/local (default)
thanx,
Hi
I am reposting this just in case someone who would be able to assist me did
not see it first time around.
Thanks
Deon.
I am currently putting together a backup system for our MySQL server. The
way I want to do this is to make use of mysqldump to perform the backup and
have the binary log
Hi There
I have only just subscribed to this list - thank you in advance for any
assistance.
I am currently putting together a backup system for our MySQL server. The
way I want to do this is to make use of mysqldump to perform the backup and
have the binary log (on a different disk to my
Anyone,
I've noticed that when I do a mysqldump, all of the backup information is
also written into the binary log. Am I doing something wrong or is there a
way to not log the mysqldump??
Thanks,
Phil
-
Before po
reverting to 'localhost' for the slave gets me to:
010611 20:40:52 Error reading packet from server: Binary log is not open (0)
Which doesn't seem right because my.cnf is specifying the binary log the
same as it ever did (when I was running an earlier MySQL version on the
machin
the mysql
client to restart the binary log before mysqlbinlog can read it, if I don't
run that and try to read the file I get the bad magic number. (ERROR: Bad
magic number; The file is probably not a MySQL binary log)
- On mysql 3.23.32 on Solaris 7 nothing works
On all versions, if I don't
On Fri, May 04, 2001 at 01:38:53AM -0400, Mike Farley wrote:
>
> Can anyone shed some light on how we should be rotating the binary
> log files?
The FLUSH LOGS command works for me.
> Try this. Enable a binary log file, then rename it to some other
> name. Then execute a flu
Subject: rotating binary log files...
Can anyone shed some light on how we should be rotating the binary log
files?
I am running version 3.23.37.
In the manual it states to flush the logs, or execute a refresh command and
that would close the existing log file and rename it to .1 extension
I am trying to restore my database using the binary
log. I have restored the last full backup and want to
rerun the updates from that point. I have tried
running this command (mysqlbinlog log-file | mysql -h
server_name), which is shown in the manual but it
doesn't seem to work.
A. Romero
> >Organization: Onet.pl - Poland
> --
> Jose A. Romero L.
> Programowanie Systemowe / IT @ Onet.pl
> [EMAIL PROTECTED]
> "It is impossible to make anything foolproof because fools are so ingenious."
> >
> >MySQL suppo
1 - 100 of 102 matches
Mail list logo
