Skip site navigation (1) Skip section navigation (2)

Re: Slow dump with pg_dump/pg_restore ? How to improve ?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: soeren(at)all-about-shift(dot)com
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Slow dump with pg_dump/pg_restore ? How to improve ?
Date: 2004-07-01 01:05:35
Message-ID: 14354.1088643935@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-general
Soeren Gerlach <soeren(at)all-about-shift(dot)com> writes:
>  * pg_dump takes 2/3 of the [single] CPU, postmaster the other 1/3 for both
>    dumps

Really!?  Hmm, that seems fairly backwards ... thinks ...

In the -Fc case this makes some amount of sense because pg_dump runs
gzip-style compression on the data (which is why the output file is
so much smaller).  But for plain text dump, pg_dump should be just
pushing the data straight through to stdout; it really ought not take
much CPU as far as I can see.  There may be some simple performance
glitch involved there.  Are you interested in recompiling with -pg
and getting a gprof profile of pg_dump?

			regards, tom lane

In response to

Responses

pgsql-general by date

Next:From: Tom LaneDate: 2004-07-01 01:17:20
Subject: Re: query failing with out of memory error message.
Previous:From: Christopher CashellDate: 2004-07-01 00:57:35
Subject: Problems restarting after database crashed (signal 11).

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group