Re: pg_dump slower than pg_restore

From: Jacob Bunk Nielsen <jacob(at)bunk(dot)cc>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_dump slower than pg_restore
Date: 2014-07-04 06:41:04
Message-ID: spamdrop+8738eh39tr.fsf@atom.bunk.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

David Wall <d(dot)wall(at)computer(dot)org> writes:

> A pg_dump backup -- with most of the data stored as large objects --
> takes about 5 hours.
>
> But restoring that dump takes about 2 hours. So it's taking 2.5 times
> longer to back it up than to restore it.

Does top(1) reveal any bottlenecks?

Is the backup constrained by CPU (top will show your backup at close to
100% CPU usage) or I/O (top will often show your process in state 'D').

I also like dstat for looking at how things play out in such situations.

Best regards

Jacob

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Albe Laurenz 2014-07-04 07:27:06 Re: Migration error " invalid byte sequence for encoding "UTF8": 0xff " from mysql 5.5 to postgresql 9.1
Previous Message David Wall 2014-07-04 05:51:29 Re: pg_dump slower than pg_restore