Re: Database Stalls

From: Mok <gurmokh(at)gmail(dot)com>
To: Shiv Iyer <shiv(at)minervadb(dot)com>
Cc: pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: Database Stalls
Date: 2023-01-30 21:31:57
Message-ID: CADko==Q32YSDTh=AHqmgxj+CVYhF2xXrgk0ruAb8oQ5qnj4_0Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Hi,

Unfortunately there is no pg_stat_activity data available as we are unaware
of the issue until it has already happened.

The version we are on is 12.11.

I don't think it is due to locks as there are none in the logs. Vacuums are
logged also and none occur before or after this event. Checkpoint timeout
is set to 1 hour and these events do not coincide with checkpoints.

Gurmokh

On Mon, 30 Jan 2023 at 18:47, Shiv Iyer <shiv(at)minervadb(dot)com> wrote:

> Hi Burmokh,
>
> Please take a look at this article copied below and ping me for further
> guidance. Thanks!
>
>
> How expensive SQLs can impact PostgreSQL Performance? -
> https://minervadb.xyz/how-expensive-sqls-can-impact-postgresql-performance/
>
>
> —
> Best
> Shiv
>
>
>
> On 30-Jan-2023, at 11:17 PM, Mok <gurmokh(at)gmail(dot)com> wrote:
>
> Hi,
>
> We've started to observe instances of one of our databases stalling for a
> few seconds.
>
> We see a spike in wal write locks then nothing for a few seconds. After
> which we have spike latency as processes waiting to get to the db can do
> so.
>
> There is nothing in the postgres logs that give us any clues to what could
> be happening, no locks, unusually high/long running transactions, just a
> pause and resume.
>
> Could anyone give me any advice as to what to look for when it comes to
> checking the underlying disk that the db is on?
>
> Thanks,
>
> Gurmokh
>
>
>
>

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Rick Otten 2023-01-30 22:47:50 Fwd: Database Stalls
Previous Message Shiv Iyer 2023-01-30 18:47:33 Re: Database Stalls