Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1isCRQ-0006q2-4W for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Jan 2020 21:12:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1isCRO-0002tX-FJ for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Jan 2020 21:12:34 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1isCRO-0002rV-5x for pgsql-hackers@lists.postgresql.org; Thu, 16 Jan 2020 21:12:34 +0000 Received: from mail-qk1-x743.google.com ([2607:f8b0:4864:20::743]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1isCRG-0001ca-PT for pgsql-hackers@lists.postgresql.org; Thu, 16 Jan 2020 21:12:33 +0000 Received: by mail-qk1-x743.google.com with SMTP id a203so20658331qkc.3 for ; Thu, 16 Jan 2020 13:12:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=8mcQHD6rEKBkWWZmHc7yxcyhfqOTUQh2KPVNj1rCGbM=; b=LiewMACuLfLmr+9qM3YNKPKbphyC3ygjJkVyMEblamRZeLFenNjH5u29h91A6yAW2t yLPodzYVtoJd51d/LYDHCtNCZZkB0wK1hvOqJjXSOnMOkcxSrUbR2go0bJVX00ZB/QJn 2HTjFjV+WINnlhnmXrbCZtVpT64AEr7NBTBmLeWJyP5TBkgijHXbY8alfxAxWchSP9eV jH8beSXtkJGr7hSIfFymdKysbXgh9FJOd250e9IQynPwS8Y3bRqpZg/0E/qYbZ9zf5pP UXaY9rXaJbA5oWEEssuHxnUtu48zvMFUwbNNKaSSFuMmpMwfjv/0C5XrBsXMooSJTonL /aPA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=8mcQHD6rEKBkWWZmHc7yxcyhfqOTUQh2KPVNj1rCGbM=; b=NZuBy2T/ewLvt+6gc0CXvqCt8DI8bJTOUlambrR44wDKATRrEdlY/s7NfQlYD37cD2 3sWbRKhNIcrVe4oThV/ehbF3m91qUmLOz/wWgwSSFMQT+2/IXCUFva/scawNxmwre6gU /b6ttMuDAFPvEZms3MQzN78TJRS+sdXVOliqNLaBUOZ1GNRElcQu6609wcNQBkPlw5ph fZaCJeKL7P5ObNPhdMBeh38miBZHaTY6iGzkk0OvlPQr46ipgAgbTzekZHDVsQinw4mu jtnaNA/iAtXMSOGRnPrUzIM//pXOjOGQ6cAmXevH44JkcsstyFUUjlFlywJeAIZ99MJk +laA== X-Gm-Message-State: APjAAAVeTlpN/E4+JHcGmVMOsNUpAskeB1WQSN1NCrQ6vGrT267gp1VM P8Xq/KGJPWR4MGtJH0b+OyXxzQ== X-Google-Smtp-Source: APXvYqziSo5KhiceLudEyGj2jcKbYSVbSF+WcmZPqqevgpbOFSkeDiVkkTwJC7QpSwZCwPghsQmRPA== X-Received: by 2002:a05:620a:94f:: with SMTP id w15mr34457341qkw.380.1579209143868; Thu, 16 Jan 2020 13:12:23 -0800 (PST) Received: from nimloth.alvh.no-ip.org ([190.217.182.135]) by smtp.gmail.com with ESMTPSA id 21sm10721217qky.41.2020.01.16.13.12.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 16 Jan 2020 13:12:23 -0800 (PST) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id B4E573008FE; Thu, 16 Jan 2020 18:05:52 -0300 (-03) Date: Thu, 16 Jan 2020 18:05:52 -0300 From: Alvaro Herrera To: Tom Lane Cc: Tomas Vondra , Fabien COELHO , vignesh C , Kyotaro Horiguchi , daniel@manitou-mail.org, peter.eisentraut@2ndquadrant.com, iwata.aya@jp.fujitsu.com, PostgreSQL Developers Subject: Re: psql - add SHOW_ALL_RESULTS option Message-ID: <20200116210552.GA23163@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4201.1579198096@sss.pgh.pa.us> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-Jan-16, Tom Lane wrote: > The compatibility issue could be resolved by putting in the option > that I suppose was there at the beginning. But then we'd have to > have a debate about which behavior would be default, and there would > still be the question of who would find this to be an improvement. > If you're chaining together commands with \; then it's likely that > you are happy with the way it behaves today. Certainly there's been > no drumbeat of bug reports about it. The patch originally submitted did indeed have the option (defaulting to "off", that is, the original behavior), and it was removed at request of reviewers Daniel Vérité, Peter Eisentraut and Kyotaro Horiguchi. My own opinion is that any scripts that rely heavily on the current behavior are stepping on shaky ground anyway. I'm not saying we should break them on every chance we get -- just that keeping them unharmed is not necessarily a priority, and that if this patch enables other psql features, it might be a good step forward. My own vote would be to use the initial patch (after applying any unrelated changes per later review), ie. add the feature with its disable button. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services