From: Tom Lane <tgl@sss.pgh.pa.us>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Mark Kirkwood <markir@paradise.net.nz>
Cc: pgsql-performance@postgresql.org, PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] fsync method checking
Date: Fri, 12 Dec 2003 16:28:47 -0500
Message-ID: <22121.1071264527@sss.pgh.pa.us> (raw)
In-Reply-To: <3FDA2B0A.1060709@colorfullife.com>
References: <200312120649.hBC6nQR15608@candle.pha.pa.us>
<3FDA2B0A.1060709@colorfullife.com>
Manfred Spraul <manfred@colorfullife.com> writes:
> One advantage of a seperate write and fsync call is better performance
> for the writes that are triggered within AdvanceXLInsertBuffer: I'm not
> sure how often that's necessary, but it's a write while holding both the
> WALWriteLock and WALInsertLock. If every write contains an implicit
> sync, that call would be much more expensive than necessary.
Ideally that path isn't taken very often. But I'm currently having a
discussion off-list with a CMU student who seems to be seeing a case
where it happens a lot. (She reports that both WALWriteLock and
WALInsertLock are causes of a lot of process blockages, which seems to
mean that a lot of the WAL I/O is being done with both held, which would
have to mean that AdvanceXLInsertBuffer is doing the I/O. More when we
figure out what's going on exactly...)
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, manfred@colorfullife.com, pgman@candle.pha.pa.us, markir@paradise.net.nz, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] fsync method checking
In-Reply-To: <22121.1071264527@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