Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qwGEj-00AfUa-V6 for pgsql-general@arkaria.postgresql.org; Fri, 27 Oct 2023 06:22:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qwGEi-00BjOX-HS for pgsql-general@arkaria.postgresql.org; Fri, 27 Oct 2023 06:22:24 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qwGEi-00BjL7-61 for pgsql-general@lists.postgresql.org; Fri, 27 Oct 2023 06:22:24 +0000 Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qwGEe-0033LX-Nr for pgsql-general@lists.postgresql.org; Fri, 27 Oct 2023 06:22:23 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type: Message-ID:References:In-Reply-To:Subject:Cc:To:From:Date:MIME-Version:Sender :Reply-To:Content-ID:Content-Description; bh=LzPm6GNXKu1IvSlX20oU7QUl/2lGuws4G7ZYmB1OIDg=; b=Avlm6l+7GYLdPQeHUbGOyCQJ4w oPoNK78hUfA+wnw5Xn5FXmhFzNlm/rbFOwZb5gC8+mtwGp/PIiu6jq+Rely8ZWdtG2EGz9fQRNz+3 i/9qXjgiuI5iOnQ4kB2No1JMppEVk1VcLmPExs2+Kh0Sk8fJ/cgcxoh0pDckfhKFLeZzb7xlS1eAo JyHf1IJACDNREODj9Bulsv8HCIJ1XB+udjKTVQsc5DXAJbmiSGKFns7BTA7PDH81Yu1ii4C+SxYK4 itoDcaWv6++KygMbuNcouH//W9GcNOpcMUB+MjMeiit+SqeBxbBta0Lk/WDjyVwdm7p7Q+t0ovj7K ayx9BMgg==; Received: from meldrar.postgresql.org ([87.238.57.231] helo=webmail.postgresql.org) by meldrar.postgresql.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qwGEa-005nVW-Qt; Fri, 27 Oct 2023 06:22:20 +0000 MIME-Version: 1.0 Date: Fri, 27 Oct 2023 16:22:16 +1000 From: Justin Clift To: pf@pfortin.com Cc: pgsql-general@lists.postgresql.org, Rick Yost Subject: Re: Disk wait problem... may not be hardware... In-Reply-To: <20231026220325.2204a3f6.pfortin@pfortin.com> References: <20231023145459.143faba7.pfortin@pfortin.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> User-Agent: Roundcube Webmail/1.4.15 Message-ID: <3c1e3b653ad983bf6bf30b3ea4bd4036@postgresql.org> X-Sender: justin@postgresql.org Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2023-10-27 12:03, pf@pfortin.com wrote: > 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