From: Ken Marshall <ktm@rice.edu>
To: pgsql-general@lists.postgresql.org
Subject: Re: Disk wait problem...
Date: Mon, 23 Oct 2023 15:09:16 -0500
Message-ID: <ZTbS7H0czxr7rSlg@aart.rice.edu> (raw)
In-Reply-To: <fe8042a8-5747-466e-ac8a-de3c5b6a469c@aklaver.com>
References: <20231023145459.143faba7.pfortin@pfortin.com>
<fe8042a8-5747-466e-ac8a-de3c5b6a469c@aklaver.com>
> Hi,
>
> I have a 1.6TB database with over 330 tables on a 4TB NVMe SSD. All
> tables are static (no updates); most in 8M and 33M row sizes. Queries have
> been great, until recently.
> Also attached is the relevant system journal entries for one query that
> took 2 seconds and two more that took 62 and 52 seconds... Unlike the
> above, these had 3 processes in disk-wait -- see attached screenshot...
>
> I just stopped PG, updated the full backup which was done overnight (so
> the update took about a second), restarted PG and the problem persists...
>
> Any suggestions where to look next?
>
> Thanks,
> Pierre
Hi Pierre,
I have seen this type of behavior when parallel queries were enabled and
PostgreSQL decided that a parallel sequential scan query was the fastest
option. Try disabling them and see if that helps.
Regards,
Ken
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: ktm@rice.edu
Subject: Re: Disk wait problem...
In-Reply-To: <ZTbS7H0czxr7rSlg@aart.rice.edu>
References: <20231023145459.143faba7.pfortin@pfortin.com> <fe8042a8-5747-466e-ac8a-de3c5b6a469c@aklaver.com> <ZTbS7H0czxr7rSlg@aart.rice.edu>
* 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