Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 461CC1FB5A4E for ; Sun, 15 Apr 2012 19:31:33 -0300 (ADT) Received: from moutng.kundenserver.de ([212.227.17.10]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SJXym-0006IY-6J for pgsql-hackers@postgresql.org; Sun, 15 Apr 2012 22:31:32 +0000 Received: from [192.168.1.6] (mail.highperformancepostgresql.com [71.179.240.8]) by mrelayeu.kundenserver.de (node=mrbap4) with ESMTP (Nemesis) id 0MHYb6-1SIQyY2ESS-003Kjg; Mon, 16 Apr 2012 00:31:11 +0200 Message-ID: <4F8B4C2D.4070400@2ndQuadrant.com> Date: Sun, 15 Apr 2012 18:31:09 -0400 From: Greg Smith User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111120 Icedove/3.1.16 MIME-Version: 1.0 To: Simon Riggs CC: Tom Lane , pgsql-hackers@postgresql.org Subject: Re: Last gasp References: <1333651599.31440.47.camel@hvost> <1333653659.31440.68.camel@hvost> <4F7E8E19.1070204@2ndQuadrant.com> <6609.1333696795@sss.pgh.pa.us> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:OOf1M2enQi0gDtDnk8Q0KZmxlDbbvpZUdKXrroFXoX3 i4UlKzLnePPmQIe1zGsLEbUXPKw5TrAW4SE1dbCAkuOSIhjXCc nPJBigwjYhCF3gH71CsaD2RJbQUWL3kdL4rOP+VF19M+9PM744 Am+iinXxujmUf14DYLelkwc6OQpmRsraHMV2zNBBf/tc9kWkis bgfA8h+XJE8dmIJT0GcvWIgX7qVerFFlL77YFk0m532GaxUtJe DlejEUAquwKdZSE0gieh/OWYkD8CZtS6n2uM9Ymy0laIZJ0lfE uXEuzxoKY9eV2O31ppJcGAn+yxUHv9oSBRrlS8K4jljEaW1fcl H6wEqNIilj9iFXsDzdVw= X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201204/791 X-Sequence-Number: 206594 On 04/15/2012 05:46 AM, Simon Riggs wrote: > Our problem is not lack of resource, it is ineffective > delegation. As Hannu points out, he didn't know the patch would be > rejected, so he didn't know help was needed to save something useful. > I considered that the job of the CF manager, but perhaps it is was > not. Note that one of the influences on the "death march" here was lack of a fully devoted CF manager for the full duration. I did some rabble rousing to get things started in the usual way, but my time for this only budgeted for six weeks in that role. And that was quite optimistic for this one. Trying to quantify how much time investment the CF manager role really involves is one of my important projects to chew on. Whoever ends up doing that should at least have an idea what scale of problem they're getting into. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.com