Re: Replication failed after stalling

From: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "Sergey Konoplev *EXTERN*" <gray(dot)ru(at)gmail(dot)com>
Cc: Joe Van Dyk *EXTERN* <joe(at)tanga(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Replication failed after stalling
Date: 2013-12-31 08:01:22
Message-ID: A737B7A37273E048B164557ADEF4A58B17C881A4@ntex2010i.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Sergey Konoplev wrote:
> On Mon, Dec 30, 2013 at 12:27 AM, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Andreas Kretschmer 2013-12-31 08:22:57 Re: Fwd: Web Hosting support for pgsql in PHP
Previous Message Sergey Konoplev 2013-12-31 06:47:31 Re: Replication failed after stalling