Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c4vEG-0005g5-Cp for pgsql-hackers@arkaria.postgresql.org; Thu, 10 Nov 2016 19:41:44 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1c4vEF-0004cY-7Y for pgsql-hackers@arkaria.postgresql.org; Thu, 10 Nov 2016 19:41:43 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1c4vCp-00033f-SE for pgsql-hackers@postgresql.org; Thu, 10 Nov 2016 19:40:16 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1c4vCn-0004UR-EZ for pgsql-hackers@postgresql.org; Thu, 10 Nov 2016 19:40:14 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id uAAJe82I009505; Thu, 10 Nov 2016 14:40:08 -0500 From: Tom Lane To: Mark Kirkwood cc: pgsql-hackers@postgresql.org Subject: Re: WIP: About CMake v2 In-reply-to: <674d4819-4453-b01a-aa7f-13215b561708@catalyst.net.nz> References: <29526280-50e2-495b-99e1-ccd4e16ffd05@postgrespro.ru> <5a8a9610-722f-49df-b609-35842fe4c8d6@postgrespro.ru> <0d8bf7e7-db42-44d8-aac5-65ff407cb60f@postgrespro.ru> <6cd3400f-a1bd-40ac-b2c9-e7e221f548eb@postgrespro.ru> <674d4819-4453-b01a-aa7f-13215b! 561708@catalyst.net.nz> Comments: In-reply-to Mark Kirkwood message dated "Fri, 11 Nov 2016 08:32:27 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <9503.1478806808.1@sss.pgh.pa.us> Date: Thu, 10 Nov 2016 14:40:08 -0500 Message-ID: <9504.1478806808@sss.pgh.pa.us> X-Pg-Spam-Score: -4.8 (----) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Mark Kirkwood writes: > I would recommend making it behave as Tom suggested. *Then* add an > --autodetect or similar option that makes > behave in the 'finding and using what it could' manner as a 2nd patch. An "--autodetect" switch would be fine with me. I just don't want it to behave that way by default, because then you get into the unexpected results problem. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers