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 1hO8Wf-00016v-OY for pgsql-hackers@arkaria.postgresql.org; Tue, 07 May 2019 22:25:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hO8Wc-0006zw-1Y for pgsql-hackers@arkaria.postgresql.org; Tue, 07 May 2019 22:25:26 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hO8Wb-0006ua-KP for pgsql-hackers@lists.postgresql.org; Tue, 07 May 2019 22:25:25 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hO8WW-0007JH-PC for pgsql-hackers@postgresql.org; Tue, 07 May 2019 22:25:24 +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 x47MPCku005222; Tue, 7 May 2019 18:25:12 -0400 From: Tom Lane To: Stephen Frost cc: Andres Freund , David Fetter , PostgreSQL Development Subject: Re: New EXPLAIN option: ALL In-reply-to: <20190507221255.GO6197@tamriel.snowman.net> References: <20190507073046.GI28936@fetter.org> <20190507154147.l32a3erg4mbycj7u@alap3.anarazel.de> <20190507163411.GM28936@fetter.org> <20190507164430.a7tig676hjzdnyyd@alap3.anarazel.de> <20190507212355.GQ28936@fetter.org> <20190507215449.3a4yb5kkoloq7yyw@alap3.anarazel.de> <4638.1557266803@sss.pgh.pa.us> <20190507221255.GO6197@tamriel.snowman.net> Comments: In-reply-to Stephen Frost message dated "Tue, 07 May 2019 18:12:56 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <5220.1557267912.1@sss.pgh.pa.us> Date: Tue, 07 May 2019 18:25:12 -0400 Message-ID: <5221.1557267912@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Stephen Frost writes: > I'm generally in favor of doing something like what Tom is suggesting > with VERBOSE, but I also feel like it should be the default for formats > like JSON. If you're asking for the output in JSON, then we really > should include everything that a flag like VERBOSE would contain because > you're pretty clearly planning to copy/paste that output into something > else to read it anyway. Meh --- I don't especially care for non-orthogonal behaviors like that. If you wanted JSON but *not* all of the additional info, how would you specify that? (The implementation I had in mind would make VERBOSE OFF more or less a no-op, so that wouldn't get you there.) >> I do feel that it's a good idea to keep ANALYZE separate. "Execute >> the query or not" is a mighty fundamental thing. I've never liked >> that name for the option though --- maybe we could deprecate it >> in favor of EXECUTE? > Let's not fool ourselves by saying we'd 'deprecate' it because that > implies, at least to me, that there's some intention of later on > removing it True, the odds of ever actually removing it are small :-(. I meant mostly changing all of our docs to use the other spelling, except for some footnote. Maybe we could call ANALYZE a "legacy spelling" of EXECUTE. regards, tom lane