| From: | Justin Pryzby <pryzby(at)telsasoft(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 17:51:18 |
| Message-ID: | 20230130175118.GE22427@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Jan 30, 2023 at 05:47:49PM +0000, Mok 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?
What version postgres? What settings have non-default values ?
What OS/version? What environment/hardware? VM/image/provider/...
Have you enabled logging for vacuum/checkpoints/locks ?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | José Arthur Benetasso Villanova | 2023-01-30 18:10:54 | Re: Database Stalls |
| Previous Message | Mok | 2023-01-30 17:47:49 | Database Stalls |