Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kIhxt-0004I2-LM for pgsql-hackers@arkaria.postgresql.org; Thu, 17 Sep 2020 00:39:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kIhxs-0002Qh-JU for pgsql-hackers@arkaria.postgresql.org; Thu, 17 Sep 2020 00:39:56 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kIhxs-0002Qa-Cc for pgsql-hackers@lists.postgresql.org; Thu, 17 Sep 2020 00:39:56 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kIhxq-0004e1-5h for pgsql-hackers@postgresql.org; Thu, 17 Sep 2020 00:39:56 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 08H0dq74066138; Wed, 16 Sep 2020 20:39:52 -0400 From: Tom Lane To: Alvaro Herrera cc: Daniel Gustafsson , Peter Eisentraut , pgsql-hackers Subject: Re: pgindent vs dtrace on macos In-reply-to: <20200917000334.GA28142@alvherre.pgsql> References: <20200917000334.GA28142@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Wed, 16 Sep 2020 21:03:34 -0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <66136.1600303192.1@sss.pgh.pa.us> Date: Wed, 16 Sep 2020 20:39:52 -0400 Message-ID: <66137.1600303192@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Alvaro Herrera writes: > On 2020-Sep-16, Tom Lane wrote: >> I think the issue is that pgindent believes "numeric" and "chr" are >> typedefs. (The regex code can be blamed for "chr", but I'm not quite >> sure where "numeric" is coming from.) > It's in src/interfaces/ecpg/include/pgtypes_numeric.h It strikes me that a low-cost workaround would be to rename these C functions. There's no law that their C names must match the SQL names. regards, tom lane