X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 6657DD1B550 for ; Fri, 10 Oct 2003 20:49:52 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 04790-04 for ; Fri, 10 Oct 2003 17:49:07 -0300 (ADT) Received: from lorax.kcilink.com (lorax.kciLink.com [206.112.95.1]) by svr1.postgresql.org (Postfix) with ESMTP id 7E35FD1B4E3 for ; Fri, 10 Oct 2003 17:49:05 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by lorax.kcilink.com (Postfix) with ESMTP id C61C03EB6 for ; Fri, 10 Oct 2003 16:49:07 -0400 (EDT) Received: from lorax.kcilink.com ([127.0.0.1]) by localhost (lorax.kcilink.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 83792-01-21 for ; Fri, 10 Oct 2003 16:49:07 -0400 (EDT) Received: from lorax.kciLink.com (localhost [127.0.0.1]) by lorax.kcilink.com (Postfix) with ESMTP id E8D593EAF for ; Fri, 10 Oct 2003 16:49:06 -0400 (EDT) Received: (from news@localhost) by lorax.kciLink.com (8.12.8p1/8.12.8/Submit) id h9AKn6CW002127 for pgsql-performance@postgresql.org; Fri, 10 Oct 2003 16:49:06 -0400 (EDT) To: pgsql-performance@postgresql.org Path: not-for-mail From: Vivek Khera Newsgroups: ml.postgres.performance Subject: Re: further testing on IDE drives Date: Fri, 10 Oct 2003 16:49:06 -0400 Organization: Khera Communications, Inc., Rockville, MD Lines: 19 Message-ID: References: <200310101724.h9AHOTs24892@candle.pha.pa.us> NNTP-Posting-Host: yertle.kcilink.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: lorax.kcilink.com 1065818946 37790 216.194.193.105 (10 Oct 2003 20:49:06 GMT) X-Complaints-To: daemon@kciLink.com NNTP-Posting-Date: Fri, 10 Oct 2003 20:49:06 +0000 (UTC) User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Portable Code, berkeley-unix) Cancel-Lock: sha1:T80+oWuac2+UQ7PTOsvmy2vaT1U= X-Virus-Scanned: by amavisd-new at kciLink.com X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/368 X-Sequence-Number: 4116 >>>>> "BM" == Bruce Momjian 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. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/