oreolek/nmig
1
0
Fork 0
Code Releases Activity

Updated README.md

Browse source
This commit is contained in:
AnatolyUss 2017-06-19 02:25:58 +03:00
parent 9887bd70c8
commit 58eaa768f9
1 changed files with 1 additions and 15 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
README.md
View file

@ -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>