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 1goVMY-00039m-GO for pgsql-hackers@arkaria.postgresql.org; Tue, 29 Jan 2019 15:31:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1goVMX-0006HA-83 for pgsql-hackers@arkaria.postgresql.org; Tue, 29 Jan 2019 15:31:45 +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 1goVMX-0006H3-0k for pgsql-hackers@lists.postgresql.org; Tue, 29 Jan 2019 15:31:45 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1goVMU-00074h-Vv for pgsql-hackers@lists.postgresql.org; Tue, 29 Jan 2019 15:31:44 +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 x0TFVdBv028719; Tue, 29 Jan 2019 10:31:39 -0500 From: Tom Lane To: Alvaro Herrera cc: pgsql-hackers@lists.postgresql.org Subject: Re: Rename nodes/relation.h => nodes/pathnodes.h ? In-reply-to: <201901281947.bv5koosxaelf@alvherre.pgsql> References: <201901281947.bv5koosxaelf@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Mon, 28 Jan 2019 16:47:15 -0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <28717.1548775899.1@sss.pgh.pa.us> Date: Tue, 29 Jan 2019 10:31:39 -0500 Message-ID: <28718.1548775899@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Alvaro Herrera writes: > On 2019-Jan-28, Tom Lane wrote: >> (There was some mention of trying to split relation.h into multiple >> files, but I fail to see any advantage in that.) > Hmm, nodes/relation.h includes lots of other files and is widely > included. Yup, that's why I'm trying to reduce the number of files that include it, over in the other thread. > If we can split it usefully, I vote for that. However, I > failed to find any concrete proposal for doing that. I don't have one > ATM but I'd like to keep the door open for it happening at some point. The door's always open, of course, but I don't see any point in waiting around for a hypothetical redesign. > I do like planner/pathnodes.h as a name, FWIW. Yeah, I think I'll go with pathnodes.h. We'd probably keep using that for the Path node typedefs themselves, even if somebody comes up with a design for splitting out other things. regards, tom lane