David Wall <d.w...@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 -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
