| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | girish R G peetle <giri(dot)anamika0(at)gmail(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL Dump rate is too slow |
| Date: | 2015-01-15 18:13:19 |
| Message-ID: | FBF0710D-8A0C-4819-B292-614251CBF814@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Jan 15, 2015, at 10:57 AM, girish R G peetle <giri(dot)anamika0(at)gmail(dot)com> 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.
> Before getting resources to setup stand by server, I just wanna make sure that we don't this issue on stand by too.
I believe he meant that pg_dump itself is the long-running transaction. Even though read-only transactions block neither readers nor writers, they still prevent cleanup of blocks because they have to be able to see the state of the db as of the beginning of the transaction.
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
http://www.elevated-dev.com/
(303) 722-0567 voice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | girish R G peetle | 2015-01-15 18:18:43 | Re: PostgreSQL Dump rate is too slow |
| Previous Message | girish R G peetle | 2015-01-15 17:57:32 | Re: PostgreSQL Dump rate is too slow |