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 1icBii-0005qP-Pj for pgsql-hackers@arkaria.postgresql.org; Tue, 03 Dec 2019 17:12:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1icBig-0002GF-1N for pgsql-hackers@arkaria.postgresql.org; Tue, 03 Dec 2019 17:12:14 +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 1icBif-0002G8-LY for pgsql-hackers@lists.postgresql.org; Tue, 03 Dec 2019 17:12:13 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1icBid-0007TJ-9M for pgsql-hackers@lists.postgresql.org; Tue, 03 Dec 2019 17:12:12 +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 xB3HC9Tb014354; Tue, 3 Dec 2019 12:12:09 -0500 From: Tom Lane To: Etsuro Fujita cc: PostgreSQL Hackers Subject: Re: Bogus EXPLAIN results with column aliases for mismatched partitions In-reply-to: References: <12424.1575168015@sss.pgh.pa.us> <4257.1575229116@sss.pgh.pa.us> <10395.1575236078@sss.pgh.pa.us> <23961.1575297703@sss.pgh.pa.us> <8343.1575323118@sss.pgh.pa.us> Comments: In-reply-to Etsuro Fujita message dated "Tue, 03 Dec 2019 13:13:43 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14352.1575393129.1@sss.pgh.pa.us> Date: Tue, 03 Dec 2019 12:12:09 -0500 Message-ID: <14353.1575393129@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Etsuro Fujita writes: > On Tue, Dec 3, 2019 at 6:45 AM Tom Lane wrote: >> Concretely, I'm thinking of the attached (on top of the other patch, >> which I just pushed). This agrees exactly with what ExplainTargetRel >> does for regular scans. > Thanks for the patch! (The patch didn't apply to HEAD cleanly, > though.) I like consistency, so +1 for the change. Yeah, 55a1954da probably changed the expected output from what that has. I'll clean it up and push. >> One could make an argument that we should schema-qualify, regardless >> of the "verbose" flag, if the output format isn't EXPLAIN_FORMAT_TEXT. >> That would reduce the amount of variability that plan analysis tools >> have to cope with. However, ExplainTargetRel itself doesn't provide >> the schema in non-verbose mode. Maybe it should, ie we should change >> it like ... > Seems like another issue to me. Agreed. When/if we change that, we could make this code follow along. regards, tom lane