| From: | Shiv Iyer <shiv(at)minervadb(dot)com> |
|---|---|
| To: | Mok <gurmokh(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Database Stalls |
| Date: | 2023-01-30 18:47:33 |
| Message-ID: | A6481438-19C9-43B9-89DB-5AF1D7130762@minervadb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mok | 2023-01-30 21:31:57 | Re: Database Stalls |
| Previous Message | José Arthur Benetasso Villanova | 2023-01-30 18:10:54 | Re: Database Stalls |