Skip site navigation (1) Skip section navigation (2)

Re: Filesystem fragmentation (Re: Fragmentation of WAL files)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: "Craig A(dot) James" <cjames(at)modgraph-usa(dot)com>, "Bill Moran" <wmoran(at)collaborativefusion(dot)com>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "Postgresql list Performance" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Filesystem fragmentation (Re: Fragmentation of WAL files)
Date: 2007-04-26 17:49:32
Message-ID: 26942.1177609772@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
Gregory Stark <stark(at)enterprisedb(dot)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

In response to

pgsql-performance by date

Next:From: Jon SimeDate: 2007-04-26 18:12:41
Subject: Re: Feature request - have postgresql log warning when new sub-release comes out.
Previous:From: Gerhard WiesingerDate: 2007-04-26 17:02:36
Subject: Re: Fw: PostgreSQL Performance Tuning

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group