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 1jnOhf-0002o8-Bs for pgsql-bugs@arkaria.postgresql.org; Mon, 22 Jun 2020 15:49:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jnOhe-0007wt-9W for pgsql-bugs@arkaria.postgresql.org; Mon, 22 Jun 2020 15:49:46 +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 1jnOhe-0007wh-3a for pgsql-bugs@lists.postgresql.org; Mon, 22 Jun 2020 15:49:46 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jnOhb-00052W-TU for pgsql-bugs@lists.postgresql.org; Mon, 22 Jun 2020 15:49:45 +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 05MFnebx2078444; Mon, 22 Jun 2020 11:49:40 -0400 From: Tom Lane To: Julien Rouhaud cc: Euler Taveira , PostgreSQL mailing lists , Maciek Sakrejda Subject: Re: BUG #16502: EXPLAIN JSON format adds extra quotes around index names In-reply-to: References: <16502-57bd1c9f913ed1d1@postgresql.org> <1816979.1592680000@sss.pgh.pa.us> <1845717.1592691069@sss.pgh.pa.us> <1882414.1592749757@sss.pgh.pa.us> Comments: In-reply-to Julien Rouhaud message dated "Sun, 21 Jun 2020 20:16:53 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2078442.1592840980.1@sss.pgh.pa.us> Date: Mon, 22 Jun 2020 11:49:40 -0400 Message-ID: <2078443.1592840980@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Julien Rouhaud writes: > On Sun, Jun 21, 2020 at 4:29 PM Tom Lane wrote: >> 2. Text-format EXPLAIN output will grow double-quotes around the >> hypothetical index names, which are not there at present (I believe, >> but didn't test it). This shouldn't bother human users particularly, >> but conceivably it might break hypopg's regression tests? > Yes, the patch is working as expected. Before: > ... > All of the regression tests except the one I added when the fix for > brin hypothetical indexes was applied are still working, as they're > looking for patterns like "Index.*<\d+>${amname}_${relname}" in the > textual explain output. There are a few fixes not released yet, so > I'll update the broken brin regression test and publish a release soon > to make sure that the packages don't get broken when the new minor > versions are released. Doesn't sound too painful then. I pushed the patch to all branches; it should appear in 13beta2 this week, and in the August quarterly updates. regards, tom lane