Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dQJAF-0007QE-NW for pgsql-hackers@arkaria.postgresql.org; Wed, 28 Jun 2017 20:02:15 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dQJAF-0005S3-3g for pgsql-hackers@arkaria.postgresql.org; Wed, 28 Jun 2017 20:02:15 +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 1dQJAE-0005RW-2j for pgsql-hackers@postgresql.org; Wed, 28 Jun 2017 20:02:14 +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 1dQJA7-0004fL-Nc for pgsql-hackers@postgresql.org; Wed, 28 Jun 2017 20:02:12 +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 v5SK23QV018013; Wed, 28 Jun 2017 16:02:03 -0400 From: Tom Lane To: Alvaro Herrera cc: Andres Freund , Jeff Janes , Michael Paquier , PostgreSQL mailing lists Subject: Re: Reducing pg_ctl's reaction time In-reply-to: <20170628194425.my75yb4lp5aerm7x@alvherre.pgsql> References: <20170628194425.my75yb4lp5aerm7x@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Wed, 28 Jun 2017 15:44:25 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <18011.1498680123.1@sss.pgh.pa.us> Date: Wed, 28 Jun 2017 16:02:03 -0400 Message-ID: <18012.1498680123@sss.pgh.pa.us> 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 Alvaro Herrera writes: > Tom Lane wrote: >> So when I removed the miscadmin.h include, I found out that pg_ctl is >> also relying on PG_BACKEND_VERSIONSTR from that file. >> >> There are at least three things we could do here: >> >> 1. Give this up as not worth this much trouble. >> >> 2. Move PG_BACKEND_VERSIONSTR into pg_config.h to go along with the >> other version-related macros. > pg_config.h sounds like a decent enough solution. It's a bit strange > this hasn't come up before, given that that symbol is used more in > frontend environ than backend. Right at the moment, what I've done is to stick it into port.h beside the declaration of find_other_exec, since the existing uses are all as parameters of find_other_exec[_or_die]. But maybe that's a bit too expedient. 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