From 51ea3130a030bfe8d37e2228ce97d5ef0b6291ac Mon Sep 17 00:00:00 2001
From: gdantkat <51437941+gdantkat@users.noreply.github.com>
Date: Sun, 20 Sep 2020 23:24:28 +0200
Subject: [PATCH] Update README.md

Chunk the pg sql COPY or INSERT statements.
In the pgfile.sql there will be only 200 lines chunks. This avoids memory issues during the
`php pg2mysql_cli.php pgfile.sql mysqlfile.sql [engine]` execution
---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 4ad3236..e9baca4 100644
--- a/README.md
+++ b/README.md
@@ -2,12 +2,12 @@
 
 ## Command-Line usage (recommended)
 
-1. `PGPASSWORD=yourpass pg_dump -h localhost --quote-all-identifiers \`
+1. `PGPASSWORD=yourpass pg_dump --rows-per-insert=200 -h localhost --quote-all-identifiers \`
     `--no-acl --no-owner --format p --data-only dbname -f pgfile.sql`
     
     Additional documentation for `pg_dump` [here](http://www.postgresql.org/docs/9.3/static/app-pgdump.html)
     
-1. `php pg2mysql_cli.php pgfile.sql mysqlfile.sql [engine]`
+2. `php pg2mysql_cli.php pgfile.sql mysqlfile.sql [engine]`
     * `pgfile.sql` will not be modified
     * `mysqlfile.sql` will be overwritten if already exists
     * engine is optional, default if not specified is InnoDB
@@ -47,4 +47,4 @@ $mysql=pg2mysql($postgres);
 Credit goes to:  
 Author: James Grant
 Lightbox Technolgoies  
-http://www.lightbox.org  
\ No newline at end of file
+http://www.lightbox.org