Date: Thu, 26 Feb 2015 10:44:33 -0500
From: "David F. Skoll" <dfs@roaringpenguin.com>
To: pgsql-admin@postgresql.org
Cc: John Scalia <jayknowsunix@gmail.com>
Subject: Re: Weird spikes in delay for async streaming replication
 on 9.1
Message-ID: <20150226104433.1b0df1db@hydrogen.roaringpenguin.com>
In-Reply-To: <54EF3E6F.60403@gmail.com>
References: <20150214110050.2f032f05@ollie.roaringpenguin.com>
 <20150226094428.34531376@hydrogen.roaringpenguin.com>
 <54EF3E6F.60403@gmail.com>
Organization: Roaring Penguin Software Inc.
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

On Thu, 26 Feb 2015 10:40:31 -0500
John Scalia <jayknowsunix@gmail.com> wrote:

> Apologies, David, but as I don't check this list very often, I
> thought you should have received an answer. Have you tried watching
> the transaction with tcpdump or wireshark?

Yes.  Haven't observed anything unusual.

> To me this sounds like either a network problem or like you're
> thinking a contention problem.

It is not a network problem; we monitor the link between sites.  And it
happens absolutely regularly, like clockwork, when we run our nightly
pg_dump on the master.

> Also, are you running streaming replication? If so, there
> shouldn't be ANY delay as the standby gets the commit before the
> primary. Otherwise, how are you replicating? -- Jay

We are running asynchronous streaming replication.

Regards,

David.


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin