Re: PostgreSQL Dump rate is too slow - Mailing list pgsql-admin

From girish R G peetle
Subject Re: PostgreSQL Dump rate is too slow
Date
Msg-id CAKKd067BaJBY2ri97=d=4B8rS-tSpmhJVL3z27umhGynup-kRg@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL Dump rate is too slow  (Scott Ribe <scott_ribe@elevated-dev.com>)
List pgsql-admin
Thanks Scott, Joshua. Got it.

On Thu, Jan 15, 2015 at 11:43 PM, Scott Ribe <scott_ribe@elevated-dev.com> wrote:
On Jan 15, 2015, at 10:57 AM, girish R G peetle <giri.anamika0@gmail.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.

pgsql-admin by date:

Previous
From: Scott Ribe
Date:
Subject: Re: PostgreSQL Dump rate is too slow
Next
From: "Joshua D. Drake"
Date:
Subject: Re: PostgreSQL Dump rate is too slow