This rading may well be some things the CSV loader does after loading: - deriving properties on the columns (sortedness, uniqueness, that sort of thing -- useful information for possibly using optimized versions of low level operators); - checking SQL-level constraints if you have specified them.
Note that if you set constraints at the SQL level (primary key, foreign key, unique), they are always checked. Either at import time when they were set during table creation, or at the time you ALTER the table to add the constraints.
On 2014-06-10 17:40, Bryan Senseman wrote:
All,
I know I have asked this before, but I am still plagued by this error. I am restoring a 50GB database from Linux to Windows, the dump file created via mclient is ~53GB. I am reading that file from an SSD and loading the database onto another SSD. This has been running for 2 DAYS! Using almost all available memory 16GB. Using Windows Resoure Monitor, the mserver5.exe process is just reading tail files for hours. The pattern is that the disk usage will grow by some amount say 5gb (I’m assuming the size of the table actually being loaded) and then it will spend 6-12 hours reading what it just wrote. Why? Can this be eliminated? I removed all indexes on the fact tables so it isn’t indexing (although that runs almost instantly anyway).
Only about 10% cpu utilization.
Thanx,
Bryan
This transmission is confidential and intended solely for the use of the recipient named above. It may contain confidential, proprietary, or legally privileged information. If you are not the intended recipient, you are hereby notified that any unauthorized review, use, disclosure or distribution is strictly prohibited. If you have received this transmission in error, please contact the sender by reply e-mail and delete the original transmission and all copies from your system.
users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list