pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Jan Gunnar Dyrset <jan.g.dyrset@cybernetica.no>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: PostgreSQL disk fragmentation causes performance problems on Windows
Date: Thu, 21 May 2015 11:54:40 -0700
Message-ID: <555E29F0.5030907@agliodbs.com> (raw)
In-Reply-To: <WM!5502dc21e8e922384b4fcf3ed42c47734f77e3ab0c80c8c587f6bab63ced852a6603e138aa8f0e70a9bf47ce43f78d81!@asav-2.01.com>
References: <AMXPR05MB120CFF5F9A4825A531E2018A1ED0@AMXPR05MB120.eurprd05.prod.outlook.com>
	<WM!5502dc21e8e922384b4fcf3ed42c47734f77e3ab0c80c8c587f6bab63ced852a6603e138aa8f0e70a9bf47ce43f78d81!@asav-2.01.com>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>

On 04/23/2015 12:47 PM, Jan Gunnar Dyrset wrote:
> I think that preallocating lumps of a given, configurable size, say 4
> MB, for the tables would remove this problem. The max number of
> fragments on a 1 GB file would then be  250, which is no problem. Is
> this possible to configure in PostgreSQL? If not, how difficult is it to
> implement in the database?

It is not currently possible to configure.

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.

Note that this could be a dead end; it's possible that preallocating
large extents could cause worse problems than the current fragmentation
issues.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



view thread (10+ messages)  latest in thread

Message-ID: <555E29F0.5030907@agliodbs.com>
Permalink:  ../555E29F0.5030907@agliodbs.com/
Also on:    postgresql.org/message-id/555E29F0.5030907@agliodbs.com

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: josh@agliodbs.com, jan.g.dyrset@cybernetica.no
  Subject: Re: PostgreSQL disk fragmentation causes performance problems on Windows
  In-Reply-To: <555E29F0.5030907@agliodbs.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