X-Original-To: pgsql-hackers-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id E43659FB2F7 for ; Mon, 4 Sep 2006 20:51:31 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 51225-10 for ; Mon, 4 Sep 2006 20:51:22 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from lists.commandprompt.com (host-130.commandprompt.net [207.173.203.130]) by postgresql.org (Postfix) with ESMTP id 2CBD79FB2D3 for ; Mon, 4 Sep 2006 20:51:22 -0300 (ADT) Received: from [192.168.1.50] (or-67-76-146-141.sta.embarqhsd.net [67.76.146.141]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id k84NpFgU021108 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Sep 2006 16:51:15 -0700 Message-ID: <44FCBC03.2000507@commandprompt.com> Date: Mon, 04 Sep 2006 16:51:31 -0700 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Thunderbird 1.5.0.5 (X11/20060728) MIME-Version: 1.0 To: Tom Lane CC: Bruce Momjian , Alvaro Herrera , Gregory Stark , pgsql-hackers@postgresql.org Subject: Re: [PATCHES] Trivial patch to double vacuum speed References: <200609042253.k84MrJp19066@momjian.us> <15844.1157413254@sss.pgh.pa.us> In-Reply-To: <15844.1157413254@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Mon, 04 Sep 2006 16:51:17 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.2 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200609/402 X-Sequence-Number: 89931 > I don't have a concrete proposal to make, but I do think that the > current patch-queue process is not suited to the project as it stands > today. Maybe if this issue-tracking stuff gets off the ground, we > could let developers place ACK or NAK flags on patches they've looked > at, and have some rule about ACK-vs-NAK requirements for something to go > in. How about *requiring* test cases that prove the patch? Sincerely, Joshua D. Drake > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster > -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/