From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | depesz(at)depesz(dot)com, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org>, Chris Wilson <chris+google(at)qwirx(dot)com> |
Subject: | Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug |
Date: | 2025-08-22 15:39:21 |
Message-ID: | 99abba30-1c14-4cc6-aef4-2f8a8f4bfac2@aklaver.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 8/22/25 08:30, hubert depesz lubaczewski wrote:
> On Fri, Aug 22, 2025 at 11:21:22AM -0400, Tom Lane wrote:
>> hubert depesz lubaczewski <depesz(at)depesz(dot)com> writes:
>>> I got repeatable case today. Is is breaking on its own everyy
>>> ~ 5 minutes.
>>
>> Interesting. That futex call is presumably caused by interaction
>> with some other process within the standby server, and the only
>> plausible candidate really is the startup process (which is replaying
>> WAL received from the primary). There are cases where WAL replay
>> will take locks that can block queries on the standby. Can you
>> correlate the delays on the standby server with any DDL events
>> occurring on the primary?
>
> Nope. Plus there is certain repetition of these cases, so even if I'd
> miss *some* create table/alter, it just isn't going to be happening
> every 4-5 minutes.
>
> So, while there are outliers, I'd say that most of the problems happens every
> 3-5 minutes.
Are you using the Postgres community version or the AWS variant?
>
> depesz
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | hubert depesz lubaczewski | 2025-08-22 15:42:08 | Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug |
Previous Message | hubert depesz lubaczewski | 2025-08-22 15:30:22 | Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug |