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 1lX0Ws-0002J3-TB for pgsql-hackers@arkaria.postgresql.org; Thu, 15 Apr 2021 11:51:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lX0Wr-0007AT-I7 for pgsql-hackers@arkaria.postgresql.org; Thu, 15 Apr 2021 11:51:25 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lX0Wr-0007AM-BT for pgsql-hackers@lists.postgresql.org; Thu, 15 Apr 2021 11:51:25 +0000 Received: from sfr-1.cri.mines-paristech.fr ([77.158.180.225] helo=smtp.cri.ensmp.fr) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lX0Wo-00030w-UX for pgsql-hackers@lists.postgresql.org; Thu, 15 Apr 2021 11:51:24 +0000 Received: from petersbourg.cri.ensmp.fr (petersbourg.cri.ensmp.fr [10.2.14.5]) by smtp.cri.ensmp.fr (Postfix) with ESMTPSA id E0014C006C; Thu, 15 Apr 2021 13:52:55 +0200 (CEST) Date: Thu, 15 Apr 2021 13:51:20 +0200 (CEST) From: Fabien COELHO X-X-Sender: fabien@pseudo To: Tom Lane cc: Michael Paquier , Alvaro Herrera , "Bossart, Nathan" , Peter Eisentraut , Julien Rouhaud , "shiy.fnst@fujitsu.com" , "pgsql-hackers@lists.postgresql.org" Subject: Re: psql - add SHOW_ALL_RESULTS option In-Reply-To: <3738387.1618451507@sss.pgh.pa.us> Message-ID: References: <69C0B369-570C-4524-8EE4-BCCACECB6BEE@amazon.com> <20210412193301.GA11204@alvherre.pgsql> <3738387.1618451507@sss.pgh.pa.us> User-Agent: Alpine 2.22 (DEB 394 2020-01-19) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello Tom, >> That's a lot IMO, so my vote would be to discard this feature for now >> and revisit it properly in the 15 dev cycle, so as resources are >> redirected into more urgent issues (13 open items as of the moment of >> writing this email). > > I don't wish to tell people which open issues they ought to work on > ... but this patch seems like it could be quite a large can of worms, > and I'm not detecting very much urgency about getting it fixed. > If it's not to be reverted then some significant effort needs to be > put into it soon. My overly naive trust in non regression test to catch any issues has been largely proven wrong. Three key features do not have a single tests. Sigh. I'll have some time to look at it over next week-end, but not before. -- Fabien.