From: | girish R G peetle <giri(dot)anamika0(at)gmail(dot)com> |
---|---|
To: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL Dump rate is too slow |
Date: | 2015-01-15 18:18:43 |
Message-ID: | CAKKd067BaJBY2ri97=d=4B8rS-tSpmhJVL3z27umhGynup-kRg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thanks Scott, Joshua. Got it.
On Thu, Jan 15, 2015 at 11:43 PM, Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
wrote:
> 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 | Joshua D. Drake | 2015-01-15 18:19:33 | Re: PostgreSQL Dump rate is too slow |
Previous Message | Scott Ribe | 2015-01-15 18:13:19 | Re: PostgreSQL Dump rate is too slow |