On Wed, Dec 18, 2013 at 3:39 PM, Sergey Konoplev <gray...@gmail.com> wrote:
> On Wed, Dec 18, 2013 at 11:26 AM, Joe Van Dyk <j...@tanga.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
