From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | girish R G peetle <giri(dot)anamika0(at)gmail(dot)com> |
Cc: | Eduardo Morras <emorrasg(at)yahoo(dot)es>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL Dump rate is too slow |
Date: | 2015-01-15 17:41:45 |
Message-ID: | 54B7FBD9.7080404@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 01/15/2015 09:21 AM, girish R G peetle wrote:
> Hi all,
> We tried pg_dump with compression level set to zero on 1TB database.
> Dump data rate started with 250GB/hr and gradually dropped to 30 GB/hr
> with 2 hours time span. We might see this behavior on standby server
> too, which will be undesirable.
>
> Any explanation on why we see this behavior ?
Because you have a long running transaction that is causing bloat to
pile up. Using pg_dump on a production database that size is a
non-starter. You need a warm/hot standby or snapshot to do this properly.
JD
--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, @cmdpromptinc
"If we send our children to Caesar for their education, we should
not be surprised when they come back as Romans."
From | Date | Subject | |
---|---|---|---|
Next Message | girish R G peetle | 2015-01-15 17:57:32 | Re: PostgreSQL Dump rate is too slow |
Previous Message | girish R G peetle | 2015-01-15 17:21:23 | Re: PostgreSQL Dump rate is too slow |