Re: Replication failed after stalling - Mailing list pgsql-general

From Albe Laurenz
Subject Re: Replication failed after stalling
Date
Msg-id A737B7A37273E048B164557ADEF4A58B17C881A4@ntex2010i.host.magwien.gv.at
Whole thread Raw
In response to Re: Replication failed after stalling  (Sergey Konoplev <gray.ru@gmail.com>)
List pgsql-general
Sergey Konoplev wrote:
> On Mon, Dec 30, 2013 at 12:27 AM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:
>> Joe Van Dyk wrote:
>>> If I run "COPY (select * from complicate_view) to stdout" on the standby, I've noticed that sometimes
>>> halts replication updates to the slave.
>>>
>>> For example, that's happening right now and "now() - pg_last_xact_replay_timestamp()" is 22 minutes.
>>> There's many transactions per second being committed on the master. Once that query is canceled, the
>>> slave catches up immediately.
>>
>> You have hot_standby_feedback = on, right?
>>
>> In that case that is expected behaviour.
>> Some change on the master conflicted with the query on the standby,
>> perhaps with a tuple cleaned up after a HOT update.  Replication will
>> stall until the query is done.
> 
> IIRC, the applying process is paused but the receiving one is going on
> in this case, isn't it?

Frankly, I don't know.

Yours,
Laurenz Albe

pgsql-general by date:

Previous
From: Sergey Konoplev
Date:
Subject: Re: Replication failed after stalling
Next
From: Andreas Kretschmer
Date:
Subject: Re: Fwd: Web Hosting support for pgsql in PHP