X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 03B3E9DC9F0 for ; Wed, 28 Dec 2005 15:24:30 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 27316-06 for ; Wed, 28 Dec 2005 15:24:30 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by postgresql.org (Postfix) with ESMTP id 070749DC845 for ; Wed, 28 Dec 2005 15:24:29 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id jBSJOSKp056723 for ; Wed, 28 Dec 2005 19:24:28 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id jBSJBmcM052553 for pgsql-admin@postgresql.org; Wed, 28 Dec 2005 19:11:48 GMT (envelope-from news) From: "Qingqing Zhou" X-Newsgroups: pgsql.admin Subject: Re: [GENERAL] Running with fsync=off Date: Wed, 28 Dec 2005 14:12:54 -0500 Organization: Hub.Org Networking Services Lines: 24 Message-ID: References: <43AA5607.20000@cs.ucr.edu> <20051222080759.GB21783@svana.org> <23560.1135270033@sss.pgh.pa.us> <20051227211238.GQ72143@pervasive.com> <4550.1135723450@sss.pgh.pa.us> X-Complaints-To: usenet@news.hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-RFC2646: Format=Flowed; Original To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=-1.408 required=5 tests=[ALL_TRUSTED=-1.44, AWL=0.032] X-Spam-Score: -1.408 X-Spam-Level: X-Archive-Number: 200512/351 X-Sequence-Number: 20071 "Tom Lane" wrote > > The actual runtime of the "sync" program is epsilon, because it doesn't > wait for all the I/O to happen. The entire reason for the custom is > that the I/O is going on while you type the second "sync". But in our 7.4.x, there is code like this: sync(); if (IsUnderPostmaster) sleep(2); sync(); So for standalone backend, that's just "sync();sync()". So the "I/O is going on while you type the second sync" theory doesn't work. For ordinary backends, that's even more wierd - Why wasting 2 seconds is enough to save the data? Why not 3 seconds or 4? Regards, Qingqing