-
-
Notifications
You must be signed in to change notification settings - Fork 525
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Duration at the summary page is wrong #1561
Comments
Output from the virtual server at my customer. Duration based on the log lines = ~ 15.5 hours |
We are having the same issues. On our end it seems that the "Create Indexes" part makes no sense. As an example, this is a summary which only migrates the schema. Real time it took was 14 sec:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I use pgloader to migrate a huge database from MariaDB to PostgreSQL. Based on the summary page, the migration takes too long, so I tried to adjust the parameters. Then I noticed that either the duration in the summary page or the times in the NOTICE lines are wrong.
The summary shows almost 8 hours, but the job took only 2,5 hours.
I can always reproduce this, even on different machines. All machines are virtual, running in rather big data centres at the office or at my customer.
pgloader version "3.6.af8c3c1"
compiled with Clozure Common Lisp Version 1.12.2 (v1.12.2) LinuxX8664
Also reproducable with the other compiler (forget the name).
did you test a fresh compile from the source tree?
yes
did you search for other similar issues?
yes, none found.
how can I reproduce the bug?
yes, always
Started with
database.load
I can't attach a database dump, because my database is over 200 GB. Using an empty database is to fast to compare the times.
I removed information about the tables because they are private.
data that is being loaded, if relevant
yes, all data has been loaded.
How the data is different from what you expected, if relevant
Does not apply.
The text was updated successfully, but these errors were encountered: