Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 58C7A9FB96B for ; Mon, 26 Feb 2007 22:26:10 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 25684-01 for ; Mon, 26 Feb 2007 22:26:01 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id A6FD59FB8E5 for ; Mon, 26 Feb 2007 22:26:06 -0400 (AST) 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 l1R2POw1017226 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 26 Feb 2007 18:25:28 -0800 Message-ID: <45E396AF.40005@commandprompt.com> Date: Mon, 26 Feb 2007 18:25:51 -0800 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Thunderbird 1.5.0.9 (X11/20070103) MIME-Version: 1.0 To: Tom Lane CC: Andrew Dunstan , pgsql-hackers@postgresql.org Subject: Re: Seeking Google SoC Mentors References: <200702261311.39684.josh@agliodbs.com> <45E34F9F.7090002@dunslane.net> <200702261550.14414.wt@penguintechs.org> <45E36722.1080703@dunslane.net> <9533.1172542238@sss.pgh.pa.us> In-Reply-To: <9533.1172542238@sss.pgh.pa.us> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88.5, clamav-milter version 0.88.5 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, 26 Feb 2007 18:25:29 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/1621 X-Sequence-Number: 99174 Tom Lane wrote: > Andrew Dunstan writes: >> Well, here's a question. Given the recent discussion re full >> disjunction, I'd like to know what sort of commitment we are going to >> give people who work on proposed projects. > > Um, if you mean are we going to promise to accept a patch in advance of > seeing it, the answer is certainly not. Still, a SoC author can improve > his chances in all the usual ways, primarily by getting discussion and > rough consensus on a spec and then on an implementation sketch before > he starts to do much code. Lots of showstopper problems can be caught > at that stage. Tom, Correct me if I am wrong, but would the way that HOT has been handled be a good way for the SoC people to do things? Joshua D. Drake > > I think the main problems with the FD patch were (1) much of the > community was never actually sold on it being a useful feature, > and (2) the implementation was not something anyone wanted to accept > into core, because of its klugy API. Both of these points could have > been dealt with before a line of code had been written, but they were > not :-( > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend > -- === 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/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/