From 58eaa768f92534206c29e6a2cb5b965b7c15cda7 Mon Sep 17 00:00:00 2001
From: AnatolyUss <you@example.comanatolyuss@gmail.com>
Date: Mon, 19 Jun 2017 02:25:58 +0300
Subject: [PATCH] Updated README.md

---
 README.md | 16 +---------------
 1 file changed, 1 insertion(+), 15 deletions(-)

diff --git a/README.md b/README.md
index f6f410e..f0e1f4d 100644
--- a/README.md
+++ b/README.md
@@ -23,7 +23,7 @@ from MySQL to PostgreSQL as easy and smooth as possible.</p>
 
 <h3>SYSTEM REQUIREMENTS</h3>
 <ul>
-<li> <b>Node.js 5 or higher</b></li>
+<li> <b>Node.js 7 or higher</b></li>
 </ul>
 
 <h3>USAGE</h3>
@@ -64,20 +64,6 @@ from MySQL to PostgreSQL as easy and smooth as possible.</p>
 <p>Current version is 3.0.0<br />
 (major version . improvements . bug fixes)</p>
 
-
-<h3>TEST</h3>
-<p>Tested using MySQL Community Server (5.7.17) and PostgreSQL (9.5).<br />
-The entire process of migration 59.9 MB database (53 tables, 581275 rows),<br />
-which includes data types mapping, creation of tables, constraints, indexes, <br />
-PKs, FKs, migration of data, garbage-collection (VACUUM) and analyzing the newly created <br />
-PostgreSQL database took 1 minute 2 seconds.</p>
-<p>
-<b>Note:</b>&nbsp; it is highly recommended to VACUUM newly created database! <br />
-Just keep in mind, that VACUUM is a very time-consuming procedure. <br />
-So if you are short in time - disable VACUUM via config.json ("no_vacuum" parameter). <br />
-Such step will save you ~25% of migration time. <br />
-</p>
-
 <h3>REMARKS</h3>
 <p>Errors/Exceptions are not passed silently.<br />
 Any error will be immediately written into the error log file.</p>