Re: Replication failed after stalling

From: Joe Van Dyk <joe(at)tanga(dot)com>
To: Sergey Konoplev <gray(dot)ru(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Replication failed after stalling
Date: 2013-12-30 05:56:04
Message-ID: CACfv+pJAxqps8MEgA5D7P78uSjO5XuL7uPXFqOq+SHBgKCA=JQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Dec 18, 2013 at 3:39 PM, Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> wrote:

> On Wed, Dec 18, 2013 at 11:26 AM, Joe Van Dyk <joe(at)tanga(dot)com> wrote:
> > I'm running Postgresql 9.3. I have a streaming replication server.
> Someone
> > was running a long COPY query (8 hours) on the standby which halted
> > replication. The replication stopped at 3:30 am. I canceled the
> long-running
> > query at 9:30 am and replication data started catching up.
>
> What do you mean by "COPY on the standby halted replication"?
>

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.

Joe

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sergey Konoplev 2013-12-30 06:52:44 Re: Replication failed after stalling
Previous Message Shiv Sharma 2013-12-29 22:54:42 Re: Do all Postgres queries touch Shared_Buffers at some point?