pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: markw@osdl.org
To: tgl@sss.pgh.pa.us
Cc: josh@agliodbs.com
Cc: Q@ping.be
Cc: pgman@candle.pha.pa.us
Cc: markir@paradise.net.nz
Cc: pgsql-performance@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] fsync method checking
Date: Mon, 22 Mar 2004 09:33:59 -0800 (PST)
Message-ID: <200403221734.i2MHYGE01546@mail.osdl.org> (raw)
In-Reply-To: <12261.1079643654@sss.pgh.pa.us>

On 18 Mar, Tom Lane wrote:
> Josh Berkus <josh@agliodbs.com> writes:
>> 1) This is an OSS project.   Why not just recruit a bunch of people on 
>> PERFORMANCE and GENERAL to test the 4 different synch methods using real 
>> databases?   No test like reality, I say ....
> 
> I agree --- that is likely to yield *far* more useful results than
> any standalone test program, for the purpose of finding out what
> wal_sync_method to use in real databases.  However, there's a second
> issue here: we would like to move sync/checkpoint responsibility into
> the bgwriter, and that requires knowing whether it's valid to let one
> process fsync on behalf of writes that were done by other processes.
> That's got nothing to do with WAL sync performance.  I think that it
> would be sensible to make a test program that focuses on this one
> specific question.  (There has been some handwaving to the effect that
> everybody knows this is safe on Unixen, but I question whether the
> handwavers have seen the internals of HPUX or AIX for instance; and
> besides we need to worry about Windows now.)

I could certainly do some testing if you want to see how DBT-2 does.
Just tell me what to do. ;)

Mark



view thread (42+ messages)  latest in thread

Message-ID: <200403221734.i2MHYGE01546@mail.osdl.org>
Permalink:  ../200403221734.i2MHYGE01546@mail.osdl.org/
Also on:    postgresql.org/message-id/200403221734.i2MHYGE01546@mail.osdl.org

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: markw@osdl.org, tgl@sss.pgh.pa.us, josh@agliodbs.com, Q@ping.be, pgman@candle.pha.pa.us, markir@paradise.net.nz, pgsql-hackers@postgresql.org
  Subject: Re: [HACKERS] fsync method checking
  In-Reply-To: <200403221734.i2MHYGE01546@mail.osdl.org>

* 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