From: Josh Berkus <josh@agliodbs.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
To: markw@osdl.org
Cc: manfred@colorfullife.com
Cc: tgl@sss.pgh.pa.us
Cc: Q@ping.be
Cc: markir@paradise.net.nz
Cc: pgsql-performance@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] fsync method checking
Date: Thu, 25 Mar 2004 11:10:55 -0800
Message-ID: <200403251110.55889.josh@agliodbs.com> (raw)
In-Reply-To: <200403251852.i2PIquv29582@candle.pha.pa.us>
References: <200403251852.i2PIquv29582@candle.pha.pa.us>
Bruce,
> We don't actually extend the WAL file during writes (preallocated), and
> the access/modification timestamp is only in seconds, so I wonder of the
> OS only updates the inode once a second. What else would change in the
> inode more frequently than once a second?
What about really big writes, when WAL files are getting added/recycled?
--
-Josh Berkus
Aglio Database Solutions
San Francisco
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, pgman@candle.pha.pa.us, markw@osdl.org, manfred@colorfullife.com, tgl@sss.pgh.pa.us, Q@ping.be, markir@paradise.net.nz, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] fsync method checking
In-Reply-To: <200403251110.55889.josh@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