Skip to content

my.cnf options - make max_binlog_size bigger #38

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 22, 2017
Merged

my.cnf options - make max_binlog_size bigger #38

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,8 +66,8 @@ Also the following MySQL config options are required:
[mysqld]
server-id = 1
log_bin = /var/lib/mysql/bin.log
expire_logs_days = 10
max_binlog_size = 100M
expire_logs_days = 30
max_binlog_size = 768M
binlog-format = row #Very important if you want to receive write, update and delete row events
```

Expand Down Expand Up @@ -98,7 +98,8 @@ Data reader understands INSERT SQL statements only. In practice this means that:

## Example

Let's walk over test example of tool launch command line options
Let's walk over test example of tool launch command line options.
This code snippet is taken from [datareader script](run_airline_ontime_data_reader.sh) shell file, described in more details in [airline.ontime Test Case](#airlineontime-test-case)

```bash
$PYTHON main.py ${*:1} \
Expand Down