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 1poaoN-0002nm-Qd for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Apr 2023 02:11:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1poaoM-0006S9-I2 for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Apr 2023 02:11:14 +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 1poaoM-0006S0-8b for pgsql-hackers@lists.postgresql.org; Tue, 18 Apr 2023 02:11:14 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1poaoJ-003XWl-JX for pgsql-hackers@postgresql.org; Tue, 18 Apr 2023 02:11:13 +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 33I2B9qe2549492; Mon, 17 Apr 2023 22:11:09 -0400 From: Tom Lane To: David Rowley cc: Alexander Lakhin , pgsql-hackers Subject: Re: Fix typos and inconsistencies for v16 In-reply-to: References: Comments: In-reply-to David Rowley message dated "Tue, 18 Apr 2023 13:35:00 +1200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2549490.1681783869.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 17 Apr 2023 22:11:09 -0400 Message-ID: <2549491.1681783869@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk David Rowley writes: > On Tue, 18 Apr 2023 at 06:00, Alexander Lakhin wro= te: >> Also, maybe OID_MAX should be removed from src/include/postgres_ext.h a= s it's unused since eb8312a22. > I didn't touch this. It seems like it could be useful for extensions > and client apps even if it's not used in core. Agreed, bad idea. For better or worse, that's part of our client API now. >> Beside that, this simple script: >> for w in $(cat src/tools/pgindent/typedefs.list); do grep -q -P "\b$w\b= " -r * --exclude typedefs.list || echo "$w"; done >> detects 58 identifiers that don't exist in the source tree anymore (see= typedefs.lost attached). >> Maybe they should be removed from typedefs.list too. > I didn't touch this either. typedefs.list normally gets some work > done during the pgindent run, which is likely going to happen around > May or June. Yeah, it will get refreshed from the buildfarm output [1] pretty soon. A quick check says that as of today, that refresh would add 81 names and remove 94. (Seems like a remarkably high number of removals, but I didn't dig further than counting the diff output.) regards, tom lane [1] https://buildfarm.postgresql.org/cgi-bin/typedefs.pl?show_list