Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 16FF5632BC9; Sun, 7 Feb 2010 14:27:44 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 46220-03; Sun, 7 Feb 2010 18:27:22 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.anarazel.de (mail.anarazel.de [217.115.131.40]) by mail.postgresql.org (Postfix) with ESMTP id 562CF63286B; Sun, 7 Feb 2010 14:27:33 -0400 (AST) Received: from alap2.localnet (e178233004.adsl.alicedsl.de [85.178.233.4]) by mail.anarazel.de (Postfix) with ESMTPSA id 1CA17448007; Sun, 7 Feb 2010 19:27:31 +0100 (CET) From: Andres Freund To: Robert Haas Subject: Re: [HACKERS] Re: Faster CREATE DATABASE by delaying fsync (was 8.4.1 ubuntu karmic slow createdb) Date: Sun, 7 Feb 2010 19:27:02 +0100 User-Agent: KMail/1.13.0 (Linux/2.6.33-rc5-andres-00243-g6ea299e; KDE/4.3.98; x86_64; ; ) Cc: Tom Lane , Greg Smith , Greg Stark , pgsql-hackers@postgresql.org, pgsql-performance@postgresql.org, Michael Clemmons , Hannu Krosing , Scott Marlowe References: <4427a97a0912101235x3ade510blcc00d5ce9883c6b6@mail.gmail.com> <24184.1265559840@sss.pgh.pa.us> <603c8f071002071023v6d5329at6f80b453f472ebb3@mail.gmail.com> In-Reply-To: <603c8f071002071023v6d5329at6f80b453f472ebb3@mail.gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201002071927.27795.andres@anarazel.de> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.363 tagged_above=-10 required=5 tests=AWL=0.236, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201002/112 X-Sequence-Number: 37533 On Sunday 07 February 2010 19:23:10 Robert Haas wrote: > On Sun, Feb 7, 2010 at 11:24 AM, Tom Lane wrote: > > Greg Smith writes: > >> This is turning into yet another one of those situations where something > >> simple and useful is being killed by trying to generalize it way more > >> than it needs to be, given its current goals and its lack of external > >> interfaces. There's no catversion bump or API breakage to hinder future > >> refactoring if this isn't optimally designed internally from day one. > > > > I agree that it's too late in the cycle for any major redesign of the > > patch. But is it too much to ask to use a less confusing name for the > > function? > > +1. Let's just rename the thing, add some comments, and call it good. Will post a updated patch in the next hours unless somebody beats me too it. Andres