pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Justin Clift <justin@postgresql.org>
To: pf@pfortin.com
Cc: pgsql-general@lists.postgresql.org, Rick Yost <Rick@ncdatateam.org>
Subject: Re: Disk wait problem...  may not be hardware...
Date: Fri, 27 Oct 2023 16:22:16 +1000
Message-ID: <3c1e3b653ad983bf6bf30b3ea4bd4036@postgresql.org> (raw)
In-Reply-To: <20231026220325.2204a3f6.pfortin@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>
	<20231026095000.4swq6vbgdsw3palp@hjp.at>
	<20231026155016.6b739a7e.pfortin@pfortin.com>
	<20231026220325.2204a3f6.pfortin@pfortin.com>

On 2023-10-27 12:03, pf@pfortin.com wrote:
<snip>
> I can't think of a common hardware bus/other that would only affect
> PostgreSQL disk accesses.

Which file system is PostgreSQL being run on?

Asking because I remember seeing weirdness reported with *some* SSD
drives when used with ZFS:

   https://github.com/openzfs/zfs/discussions/14793

Note - that's not PostgreSQL specific or anything, but more of a
"weird stuff showing up with NVMe drives" thing.

Regards and best wishes,

Justin Clift





view thread (9+ messages)  latest in thread

Message-ID: <3c1e3b653ad983bf6bf30b3ea4bd4036@postgresql.org>
Permalink:  ../3c1e3b653ad983bf6bf30b3ea4bd4036@postgresql.org/
Also on:    postgresql.org/message-id/3c1e3b653ad983bf6bf30b3ea4bd4036@postgresql.org

 · 

reply

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: justin@postgresql.org, pf@pfortin.com, Rick@ncdatateam.org
  Subject: Re: Disk wait problem...  may not be hardware...
  In-Reply-To: <3c1e3b653ad983bf6bf30b3ea4bd4036@postgresql.org>
  References: <20231023145459.143faba7.pfortin@pfortin.com> <fe8042a8-5747-466e-ac8a-de3c5b6a469c@aklaver.com> <20231023175529.59f309bb@pfortin.com> <9938ff1a-8837-454b-a50c-a748e84c172a@aklaver.com> <20231026095000.4swq6vbgdsw3palp@hjp.at> <20231026155016.6b739a7e.pfortin@pfortin.com> <20231026220325.2204a3f6.pfortin@pfortin.com> <3c1e3b653ad983bf6bf30b3ea4bd4036@postgresql.org>

* 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