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 1nIvb8-0001mP-NG for pgsql-hackers@arkaria.postgresql.org; Sat, 12 Feb 2022 16:50:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nIvb7-0002Ie-N2 for pgsql-hackers@arkaria.postgresql.org; Sat, 12 Feb 2022 16:50:09 +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 1nIvb7-0002IU-EB for pgsql-hackers@lists.postgresql.org; Sat, 12 Feb 2022 16:50:09 +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 1nIvb5-0005gI-6H for pgsql-hackers@lists.postgresql.org; Sat, 12 Feb 2022 16:50:09 +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 21CGo0sn2282967; Sat, 12 Feb 2022 11:50:00 -0500 From: Tom Lane To: Christoph Berg cc: Michael Paquier , pgsql-hackers@lists.postgresql.org Subject: Re: pgsql: Add TAP test to automate the equivalent of check_guc In-reply-to: References: <2280644.1644683003@sss.pgh.pa.us> Comments: In-reply-to Christoph Berg message dated "Sat, 12 Feb 2022 17:31:55 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2282965.1644684600.1@sss.pgh.pa.us> Date: Sat, 12 Feb 2022 11:50:00 -0500 Message-ID: <2282966.1644684600@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Christoph Berg writes: > I was confusing that with this: The problem that led to the pg_config > patch years ago was that we have a /usr/bin/pg_config in > (non-major-version-dependant) libpq-dev, and > /usr/lib/postgresql/NN/bin/pg_config in the individual > postgresql-server-dev-NN packages, and iirc the /usr/bin version > didn't particularly like the other binaries being in > /usr/lib/postgresql/NN/bin/. Ah. That seems a bit problematic anyway ... if the version-dependent pg_configs don't all return identical results, what's the non-version-dependent one supposed to do? regards, tom lane