Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YvXFR-0006Eh-B9 for pgsql-performance@arkaria.postgresql.org; Thu, 21 May 2015 20:39:21 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YvXFQ-000405-QR for pgsql-performance@arkaria.postgresql.org; Thu, 21 May 2015 20:39:20 +0000 Received: from makus.postgresql.org ([174.143.35.229]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YvXFP-0003xh-Hn for pgsql-performance@postgresql.org; Thu, 21 May 2015 20:39:19 +0000 Received: from mail.anarazel.de ([217.115.131.40]) by makus.postgresql.org with esmtp (Exim 4.84) (envelope-from ) id 1YvXFN-0005zs-7p for pgsql-performance@postgresql.org; Thu, 21 May 2015 20:39:18 +0000 Received: from intern.anarazel.de (unknown [184.23.178.130]) (Authenticated sender: andres@anarazel.de) by mail.anarazel.de (Postfix) with ESMTPSA id 1E003860003; Thu, 21 May 2015 22:39:15 +0200 (CEST) Date: Thu, 21 May 2015 22:39:13 +0200 From: Andres Freund To: Josh Berkus Cc: Jan Gunnar Dyrset , "pgsql-performance@postgresql.org" Subject: Re: PostgreSQL disk fragmentation causes performance problems on Windows Message-ID: <20150521203913.GB2028@alap3.anarazel.de> References: <555E29F0.5030907@agliodbs.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <555E29F0.5030907@agliodbs.com> X-Pg-Spam-Score: -4.2 (----) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On 2015-05-21 11:54:40 -0700, Josh Berkus wrote: > This has been talked about as a feature, but would require major work on > PostgreSQL to make it possible. You'd be looking at several months of > effort by a really good hacker, and then a whole bunch of performance > testing. If you have the budget for this, then please let's talk about > it because right now nobody is working on it. I think this is overestimating the required effort quite a bit. While not trivial, it's also not that complex to make this work. Greetings, Andres Freund -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance