From: Justin Pryzby <pryzby@telsasoft.com>
To: Mok <gurmokh@gmail.com>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: Database Stalls
Date: Mon, 30 Jan 2023 11:51:18 -0600
Message-ID: <20230130175118.GE22427@telsasoft.com> (raw)
In-Reply-To: <CADko==RNKpURpjfLDOKDLo5uaAh9gNC9y+nkTcrvjp_nxGf_FQ@mail.gmail.com>
References: <CADko==RNKpURpjfLDOKDLo5uaAh9gNC9y+nkTcrvjp_nxGf_FQ@mail.gmail.com>
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 ?
https://wiki.postgresql.org/wiki/Slow_Query_Questions
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: pgsql-performance@postgresql.org
Cc: pryzby@telsasoft.com, gurmokh@gmail.com, pgsql-performance@lists.postgresql.org
Subject: Re: Database Stalls
In-Reply-To: <20230130175118.GE22427@telsasoft.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox