Re: pg_dump on Hot standby : clarification on how to

From: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_dump on Hot standby : clarification on how to
Date: 2011-05-13 00:08:18
Message-ID: 20110513000817.GC47313@shinkuro.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, May 12, 2011 at 11:26:38AM -0700, bubba postgres wrote:
> I would just like to get some clarification from the list on how to do a
> pg_dump on the slave in the face of "canceling statement due to conflict
> with recovery".
> The following links seem to indicate that If I start an idle transaction on
> the master I should be able to do the pg_dump, but I tried this in psql on
> the master "start transaction", and was still unable to do a pg_dump on the
> slave at the same time.
> Is there something special about using dblink that would make this all work?

Could you define what you mean by "unable to do pg_dump on the slave"?

I don't see why dblink would be the special thing. I think what you
want is to hold a transaction open on the master so that the WAL can't
get recycled. At least, that's what I understood from the post. I
haven't actually tried it yet, but to me it sounded like it ought to
work.

A

--
Andrew Sullivan
ajs(at)crankycanuck(dot)ca

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Eric Hu 2011-05-13 00:30:47 Re: How to handle bogus nulls from ActiveRecord
Previous Message Tomas Vondra 2011-05-12 20:09:34 Re: Massive delete from a live production DB