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 1pyZCA-0003Ya-8F for pgsql-hackers@arkaria.postgresql.org; Mon, 15 May 2023 14:29:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pyZC8-00037Y-8Y for pgsql-hackers@arkaria.postgresql.org; Mon, 15 May 2023 14:29:00 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pyZC8-00037P-04 for pgsql-hackers@lists.postgresql.org; Mon, 15 May 2023 14:29:00 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pyZC5-002T9R-Gn for pgsql-hackers@lists.postgresql.org; Mon, 15 May 2023 14:28:58 +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 34FESqqe2153026; Mon, 15 May 2023 10:28:52 -0400 From: Tom Lane To: Alvaro Herrera cc: Laurenz Albe , Pavel Stehule , Kirk Wolak , PostgreSQL Hackers Subject: Re: psql: Could we get "-- " prefixing on the **** QUERY **** outputs? (ECHO_HIDDEN) In-reply-to: <20230515141457.ovpznndsvulahbpk@alvherre.pgsql> References: <20230515141457.ovpznndsvulahbpk@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Mon, 15 May 2023 16:14:57 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2153024.1684160932.1@sss.pgh.pa.us> Date: Mon, 15 May 2023 10:28:52 -0400 Message-ID: <2153025.1684160932@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Alvaro Herrera writes: > It's worth considering what will readline history do with the comment. > As I recall, we keep /* comments */ together with the query that > follows, but the -- comments are keep in a separate history entry. > So that's one more reason to prefer /* */ Good point. > (To me, that also suggests to remove the asterisk line after each query, > and to keep just the one before.) Meh ... the one after serves to separate a query from its output. regards, tom lane