From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Vivek Khera <khera@kcilink.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: further testing on IDE drives
Date: Fri, 10 Oct 2003 17:22:57 -0400 (EDT)
Message-ID: <200310102122.h9ALMvo12903@candle.pha.pa.us> (raw)
In-Reply-To: <x7smm0om2l.fsf@yertle.int.kciLink.com>
Vivek Khera wrote:
> >>>>> "BM" == Bruce Momjian <pgman@candle.pha.pa.us> writes:
>
> >> Sounds reasonable to me. Are there many / any scenarios where a plain
> >> fsync would be faster than open_sync?
>
> BM> Yes. If you were doing multiple WAL writes before transaction fsync,
> BM> you would be fsyncing every write, rather than doing two writes and
> BM> fsync'ing them both. I wonder if larger transactions would find
> BM> open_sync slower?
>
> consider loading a large database from a backup dump. one big
> transaction during the COPY. I don't know the implications it has on
> this scenario, though.
COPY only does fsync on COPY completion, so I am not sure there are
enough fsync's there to make a difference.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
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: pgman@candle.pha.pa.us, khera@kcilink.com
Subject: Re: further testing on IDE drives
In-Reply-To: <200310102122.h9ALMvo12903@candle.pha.pa.us>
References: <x7smm0om2l.fsf@yertle.int.kciLink.com> <200310102122.h9ALMvo12903@candle.pha.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