Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bNQXX-0008AR-BV for pgsql-hackers@arkaria.postgresql.org; Wed, 13 Jul 2016 20:13:51 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bNQXW-0001OY-Rb for pgsql-hackers@arkaria.postgresql.org; Wed, 13 Jul 2016 20:13:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bNQXW-0001OI-97 for pgsql-hackers@postgresql.org; Wed, 13 Jul 2016 20:13:50 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bNQXT-00089W-9X for pgsql-hackers@postgresql.org; Wed, 13 Jul 2016 20:13:49 +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 u6DKDhLW032592; Wed, 13 Jul 2016 16:13:43 -0400 From: Tom Lane To: Robert Haas cc: Fabien COELHO , Pavel Stehule , PostgreSQL Developers Subject: Re: pgbench - allow to store select results into variables In-reply-to: References: <32184.1468440143@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Wed, 13 Jul 2016 15:07:16 -0500" Date: Wed, 13 Jul 2016 16:13:43 -0400 Message-ID: <32591.1468440823@sss.pgh.pa.us> X-Pg-Spam-Score: -3.2 (---) 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 Wed, Jul 13, 2016 at 3:02 PM, Tom Lane wrote: >> I note also that we were talking a couple months ago >> about trying to align psql and pgbench backslash commands more closely. >> This would not be a good step in that direction. > True, but I'd still argue that \into is a lot more readable than > \gset. Maybe both programs should support both commands. Meh, personal preference there no doubt. I'd be okay with both programs supporting both commands, but the \into command as described here would be quite unreasonable to implement in psql. It needs to act more like a semicolon-substitute, as \g and the rest of its family do. (I think I'd also lobby for spelling it \ginto.) 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