public inbox for [email protected]  

help / color / mirror / Atom feed

From: Adrian Klaver <[email protected]>
To: [email protected]
Cc: PostgreSQL General <[email protected]>
Subject: Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
Date: Wed, 20 Aug 2025 10:45:13 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On 8/20/25 09:08, hubert depesz lubaczewski wrote:
> On Wed, Aug 20, 2025 at 08:14:47AM -0700, Adrian Klaver wrote:
>> Hmm.
>>
>>  From initial post:
>>
>> "For ~ 1 second there are no logs going to log (we usually have at 5-20
>> messages logged per second), no connection, nothing. And then we get
>> bunch (30+) messages with the same milisecond time."
>>
>> Are the 30+ messages all coming in on one connection or multiple
>> connections?
> 
> Multiple connections.
> 
>> Also to be clear these are statements that are being run on the replica
>> locally, correct?
> 
> What do you mean locally?

I should have been clearer. Are the queries being run against the 
replica or the primary?

> 
> Application servers are *not* on the same server as the db. So no, they
> are not local.

Where are the application servers relative to the replica server?

How many applications servers are hitting the database?

> 
>> Does the AWS monitoring indicate any issues?
> 
> Nope. All looks "fine".


> 
> Same for our monitoring  - CPU usage, iops, load.
> 
> Best regards,
> 
> depesz
> 


-- 
Adrian Klaver
[email protected]

view thread (27+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox