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 1qwapG-00CziQ-1F for pgsql-general@arkaria.postgresql.org; Sat, 28 Oct 2023 04:21:30 +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 1qwapD-002yiB-FU for pgsql-general@arkaria.postgresql.org; Sat, 28 Oct 2023 04:21:27 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qwapB-002yi3-Eh for pgsql-general@lists.postgresql.org; Sat, 28 Oct 2023 04:21:27 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qwap8-002fxe-0Y for pgsql-general@lists.postgresql.org; Sat, 28 Oct 2023 04:21:24 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 6FBF55C0120; Sat, 28 Oct 2023 00:21:20 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sat, 28 Oct 2023 00:21:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1698466880; x=1698553280; bh=9zEPjJ3j0inPjvxPC2Rv3uAIO911kgP8nle SuL0HdF0=; b=ND1dgzmAUnrZeqhfI7ho7UA4Th2cSQWXdC9ui+dc3DUafwSWzLh cAeC+d26vYlregSquBBDLk1jSkEJeSZrXKWltmZMsovbHBu+JeOVdMfJVguPTGSa kB73FV8IoTUb4xO6z8+a8KaVokEFtnHtDvDesvgDlF+Q+edwfpjjI/c6zVPq2Vx/ sinLzjucDITpSjdWj7aNaPDzxVpihwT3Xx23jMr7ZgOm7+U9upPp5mBc3dPzaH8C r1yGyDt4xtw0h2HV3PoKLVw/4BMvFQcNvhik3qPe6nlVeo3vikTfvpr1yke2LmMf g1yFY6B393Ur9uywiOHUj4bjwXzlfIQQRDg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1698466880; x= 1698553280; bh=9zEPjJ3j0inPjvxPC2Rv3uAIO911kgP8nleSuL0HdF0=; b=o 9buK+22h7qvufDI1+9gwuLhMaQPBzourUmOgNZPiMTDMI8DZ9aONPz4yriUjd8QE XDquwKROvY1+3+72XiCRASUoKFOMfAiDNMjjDTProc+mjOZa63J/U+xDpnZcRb2m djb+64mLhqw2wwmBkBEKbXiXPXveXpydrFe7B4HDoXChPD6VY9jLkEr7rmVPknSH YYCnNobOzfv5CGNyVAXw48aTrGRRBqvWtYhDtaUD3VqgJvCfqovjCpOXH8xuNkPv eZAzpuq9sj3h99hTSGWauYqf00fYvuWP4Mclxs9CIudr7zz39QByQCdWMtusuk7U CumJt1wMadMEbLYalerZQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrleehgdekudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesthejre dttddvjeenucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhl rghvvghrsegrkhhlrghvvghrrdgtohhmqeenucggtffrrghtthgvrhhnpeeivdfhieehhe egueeileejieettdejhedugeefleekvdelkeehtdfgiefffeekudenucevlhhushhtvghr ufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvg hrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 28 Oct 2023 00:21:19 -0400 (EDT) Message-ID: <10ba07cd-8cf3-4854-ac3f-247e243297dd@aklaver.com> Date: Fri, 27 Oct 2023 21:21:18 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Disk wait problem... may not be hardware... To: pf@pfortin.com, pgsql-general@lists.postgresql.org 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> <20231027170711.xgz3xrf7cujx7udh@hjp.at> <20231027194609.1bf96324.pfortin@pfortin.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: <20231027194609.1bf96324.pfortin@pfortin.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 10/27/23 16:46, pf@pfortin.com wrote: > Peter, > > Thanks for your patience; I've been feeling pressure to get this > resolved; so have been lax in providing info here.. Hope the following > helps... > > Something I hadn't noticed before: SQL-workbench/J (build 129.6) displays > an execution timer at the bottom of the window. I see all the queries > reporting 0-47ms which it plenty fast. It's the results that often take a > long time to display. Which is not surprising as building GUI elements is an expensive operation. If the time to display is your wait issue then this is not really a disk issue. What happens if you use psql as the client? -- Adrian Klaver adrian.klaver@aklaver.com