| 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 18:19:33 |
| Message-ID: | 54B804B5.70305@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 01/15/2015 09:57 AM, girish R G peetle wrote:
> Thanks Joshua. Even if we have a long transaction running on the
> database, pg_dump shouldn't be affected right ? As it doesn't block
> readers or writers.
Correct. It does not block readers or writers, it does however block
routine maintenance most of the time, which will cause bloat to pile up,
making your reads (and writes) go slower as the pages become more
fragmented.
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 | John Scalia | 2015-01-16 15:56:19 | Back to my pg_upgrade stoppage problem |
| Previous Message | girish R G peetle | 2015-01-15 18:18:43 | Re: PostgreSQL Dump rate is too slow |