Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dlNMA-0002gV-Jw for pgsql-hackers@arkaria.postgresql.org; Fri, 25 Aug 2017 22:45:38 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dlNMA-0005fC-2y for pgsql-hackers@arkaria.postgresql.org; Fri, 25 Aug 2017 22:45:38 +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 1dlNKd-0002sC-9Y for pgsql-hackers@postgresql.org; Fri, 25 Aug 2017 22:44:03 +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 1dlNKZ-0005NA-E9 for pgsql-hackers@postgresql.org; Fri, 25 Aug 2017 22:44:02 +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 v7PMhsxS014597; Fri, 25 Aug 2017 18:43:54 -0400 From: Tom Lane To: Robert Haas cc: Fabien COELHO , Pavel Stehule , Corey Huinker , Daniel Verite , PostgreSQL Developers Subject: Re: Variable substitution in psql backtick expansion In-reply-to: References: <3926.1491159242@sss.pgh.pa.us> <13303.1503698976@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Fri, 25 Aug 2017 18:22:03 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14595.1503701034.1@sss.pgh.pa.us> Date: Fri, 25 Aug 2017 18:43:54 -0400 Message-ID: <14596.1503701034@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 Robert Haas writes: > On Fri, Aug 25, 2017 at 6:09 PM, Tom Lane wrote: >> ... I'm still not sure that there's any use case for the >> string versions ("9.6.4" etc). > If somebody's doing comparisons, they probably want the numeric > version, but somebody might want to print the string version in an > error message e.g. \if \echo this thing > doesn't work on :VERSION_NAME \quit \endif OK, but if human-friendly display is the use-case then it ought to duplicate what psql itself would print in, eg, the startup message about server version mismatch. The v4 patch does not, in particular it neglects PQparameterStatus(pset.db, "server_version"). This would result in printing, eg, "11.0" when the user would likely rather see "11devel". 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