From: Tom Lane <tgl@sss.pgh.pa.us>
To: Gregory Stark <stark@enterprisedb.com>
Cc: Craig A. James <cjames@modgraph-usa.com>
Cc: Bill Moran <wmoran@collaborativefusion.com>
Cc: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: Postgresql list Performance <pgsql-performance@postgresql.org>
Subject: Re: Filesystem fragmentation (Re: Fragmentation of WAL files)
Date: Thu, 26 Apr 2007 13:49:32 -0400
Message-ID: <26942.1177609772@sss.pgh.pa.us> (raw)
In-Reply-To: <87wszz6q1q.fsf@oxford.xeocode.com>
References: <3BD44C5D-E402-43EB-8FFD-1A4BC97AFD0C@decibel.org>
<20070426080050.522ef7b5.wmoran@collaborativefusion.com>
<463096AD.4020707@enterprisedb.com>
<20070426091432.274977fe.wmoran@collaborativefusion.com>
<4630D4B6.9040802@modgraph-usa.com>
<87wszz6q1q.fsf@oxford.xeocode.com>
Gregory Stark <stark@enterprisedb.com> writes:
> In the case of a performance-critical file like the WAL that's always read
> sequentially it may be to our advantage to defeat this technique and force it
> to be allocated sequentially. I'm not sure whether any filesystems provide any
> option to do so.
We more or less do that already by filling the entire file in one go
when it's created ...
regards, tom lane
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: tgl@sss.pgh.pa.us, stark@enterprisedb.com, cjames@modgraph-usa.com, wmoran@collaborativefusion.com, heikki@enterprisedb.com
Subject: Re: Filesystem fragmentation (Re: Fragmentation of WAL files)
In-Reply-To: <26942.1177609772@sss.pgh.pa.us>
* 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