pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Steinar H. Gunderson <sgunderson@bigfoot.com>
To: Csaba Nagy <nagy@ecircle-ag.com>
To: Mikael Carneholm <Mikael.Carneholm@WirelessCar.com>
To: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: Migration study, step 1: bulk write performance
Date: Tue, 21 Mar 2006 13:10:32 +0100
Message-ID: <20060321121032.GB12963@uio.no> (raw)
In-Reply-To: <20060321120158.GO15742@pervasive.com>
References: <7F10D26ECFA1FB458B89C5B4B0D72C2B088286@sesrv12.wirelesscar.com>
	<1142867952.16487.96.camel@coppola.muc.ecircle.de>
	<20060321112759.GF15742@pervasive.com>
	<1142941966.23597.4.camel@coppola.muc.ecircle.de>
	<20060321115618.GA12880@uio.no>
	<20060321120158.GO15742@pervasive.com>

On Tue, Mar 21, 2006 at 06:01:58AM -0600, Jim C. Nasby wrote:
> Are you sure? Metadate changes are probably a lot more common on the WAL
> partition. In any case, I don't see why there should be a difference.
> The real issue is: is related filesystem metadata sync'd as part of a
> file being fsync'd?

I've been told on this list that PostgreSQL actually takes care to fill a new
WAL file with zeroes etc. when initializing it; dig a few months back and I'm
sure it's there.

/* Steinar */
-- 
Homepage: http://www.sesse.net/



view thread (26+ messages)  latest in thread

Message-ID: <20060321121032.GB12963@uio.no>
Permalink:  ../20060321121032.GB12963@uio.no/
Also on:    postgresql.org/message-id/20060321121032.GB12963@uio.no

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: sgunderson@bigfoot.com, nagy@ecircle-ag.com, Mikael.Carneholm@WirelessCar.com
  Subject: Re: Migration study, step 1: bulk write performance
  In-Reply-To: <20060321121032.GB12963@uio.no>
  References: <7F10D26ECFA1FB458B89C5B4B0D72C2B088286@sesrv12.wirelesscar.com> <1142867952.16487.96.camel@coppola.muc.ecircle.de> <20060321112759.GF15742@pervasive.com> <1142941966.23597.4.camel@coppola.muc.ecircle.de> <20060321115618.GA12880@uio.no> <20060321120158.GO15742@pervasive.com> <20060321121032.GB12963@uio.no>

* 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