Re: pg_dump slower than pg_restore - Mailing list pgsql-general

From Jacob Bunk Nielsen
Subject Re: pg_dump slower than pg_restore
Date
Msg-id spamdrop+8738eh39tr.fsf@atom.bunk.cc
Whole thread Raw
In response to pg_dump slower than pg_restore  (David Wall <d.wall@computer.org>)
List pgsql-general
David Wall <d.wall@computer.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



pgsql-general by date:

Previous
From: David Wall
Date:
Subject: Re: pg_dump slower than pg_restore
Next
From: Albe Laurenz
Date:
Subject: Re: Migration error " invalid byte sequence for encoding "UTF8": 0xff " from mysql 5.5 to postgresql 9.1