From: pf@pfortin.com
To: pgsql-general@lists.postgresql.org
Subject: Re: Disk wait problem...
Date: Mon, 23 Oct 2023 20:03:16 -0400
Message-ID: <20231023200316.194b9e3d@pfortin.com> (raw)
In-Reply-To: <9938ff1a-8837-454b-a50c-a748e84c172a@aklaver.com>
References: <20231023145459.143faba7.pfortin@pfortin.com>
<fe8042a8-5747-466e-ac8a-de3c5b6a469c@aklaver.com>
<20231023175529.59f309bb@pfortin.com>
<9938ff1a-8837-454b-a50c-a748e84c172a@aklaver.com>
On Mon, 23 Oct 2023 16:31:30 -0700 Adrian Klaver wrote:
>Please reply to list also.
>Ccing the list for this post.
Sorry, got the list's message and one directly from you; looks like I
picked the wrong one to reply to...
I just heard from a remote team member who wrote this:
!! Eventually found that 3 PG processes are sitting in disk-wait
(attached
!! screenshot)... I still can't imagine what would hold onto a
disk for that
!! long,
I wonder if these are abandoned queries that did not properly close
out.
He forgot to attach his screenshot; trying to get more info from him...
Thanks,
Pierre
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: pf@pfortin.com
Subject: Re: Disk wait problem...
In-Reply-To: <20231023200316.194b9e3d@pfortin.com>
References: <20231023145459.143faba7.pfortin@pfortin.com> <fe8042a8-5747-466e-ac8a-de3c5b6a469c@aklaver.com> <20231023175529.59f309bb@pfortin.com> <9938ff1a-8837-454b-a50c-a748e84c172a@aklaver.com> <20231023200316.194b9e3d@pfortin.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