Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hsosa-0008J8-84 for pgsql-hackers@arkaria.postgresql.org; Wed, 31 Jul 2019 13:42:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hsosY-00011p-Ug for pgsql-hackers@arkaria.postgresql.org; Wed, 31 Jul 2019 13:42:54 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hsosY-00011h-II for pgsql-hackers@lists.postgresql.org; Wed, 31 Jul 2019 13:42:54 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1hsosW-0001rb-68 for pgsql-hackers@postgresql.org; Wed, 31 Jul 2019 13:42:53 +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 x6VDgiwA022398; Wed, 31 Jul 2019 09:42:44 -0400 From: Tom Lane To: Michael Paquier cc: Amit Kapila , vignesh C , Pg Hackers Subject: Re: Unused header file inclusion In-reply-to: <20190731063749.GQ1577@paquier.xyz> References: <20190731055630.GO1577@paquier.xyz> <20190731063749.GQ1577@paquier.xyz> Comments: In-reply-to Michael Paquier message dated "Wed, 31 Jul 2019 15:37:49 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <22396.1564580564.1@sss.pgh.pa.us> Date: Wed, 31 Jul 2019 09:42:44 -0400 Message-ID: <22397.1564580564@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Michael Paquier writes: > On Wed, Jul 31, 2019 at 11:55:37AM +0530, Amit Kapila wrote: >> If we can come up with some such tool, we might be able to integrate >> it with Thomas's patch tester [1] wherein it can apply the patch, >> verify if there are unnecessary includes in the patch and report the >> same. > Or even get something into src/tools/? If the produced result is > clean enough, that could be interesting. I take it nobody has actually bothered to *look* in src/tools. src/tools/pginclude/README Note that our experience with this sort of thing has not been very good. See particularly 1609797c2. regards, tom lane