From 646a39a5b0ede1f68ef51edaeb843b6c18b225e9 Mon Sep 17 00:00:00 2001 From: Federico Campoli Date: Sun, 2 Apr 2017 11:02:56 +0100 Subject: [PATCH] fix typo (damn dyslexia) --- README.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.rst b/README.rst index d9d1f3e3..56bfc07b 100644 --- a/README.rst +++ b/README.rst @@ -56,7 +56,7 @@ What doesn't work Caveats .............................. The copy_max_memory is just an estimate. The average rows size is extracted from mysql's informations schema and can be outdated. -If the copy process fails for memory errpr check the failing table's row length and the number of rows for each slice. +If the copy process fails for memory error check the failing table's row length and the number of rows for each slice. The batch is processed every time the replica stream is empty, when a DDL is captured or when the MySQL switches to another log segment (ROTATE EVENT). Therefore the replica_batch_size is just the high watermark. The parameter controls also the size of the batch replayed by pg_engine.process_batch.