I just checked my latest dump attempt and it has now spent 128077
seconds trying to dump the 29GB table and making almost no progress (1
row every 30 seconds as estimated by strace). I guess the MVCC
implementation is pushed to its limits because I can see other queries
not finishing in a timel
Mathieu Bruneau wrote:
> I never experience any dump that were slow due to the index. The index
> aren't dumped anyway they will be recreate when you import them back so
> it shouldn't matter. (And that will cause problem if the db is running)
> so I wouldn't drop the index on your table if I were
I never experience any dump that were slow due to the index. The index
aren't dumped anyway they will be recreate when you import them back so
it shouldn't matter. (And that will cause problem if the db is running)
so I wouldn't drop the index on your table if I were you...
Your getting a lot of c
Try dropping the indexes first if you can, would save you about half the
time and then re-build them after the dump finishes. Obviously you
would need to do it at a quite time though when the DB is not being
used. Is a binary backup not an option? at 29G is a large text file to
write
Ade
D
