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 1go8gY-0005t8-RY for pgsql-hackers@arkaria.postgresql.org; Mon, 28 Jan 2019 15:18:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1go8gW-0002CQ-MC for pgsql-hackers@arkaria.postgresql.org; Mon, 28 Jan 2019 15:18:52 +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 1go8gW-0002CI-Ez for pgsql-hackers@lists.postgresql.org; Mon, 28 Jan 2019 15:18:52 +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 1go8gU-0006Rz-8y for pgsql-hackers@lists.postgresql.org; Mon, 28 Jan 2019 15:18:51 +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 x0SFImC4007720 for ; Mon, 28 Jan 2019 10:18:48 -0500 From: Tom Lane To: pgsql-hackers@lists.postgresql.org Subject: Rename nodes/relation.h => nodes/pathnodes.h ? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7718.1548688728.1@sss.pgh.pa.us> Date: Mon, 28 Jan 2019 10:18:48 -0500 Message-ID: <7719.1548688728@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk In the pluggable-storage discussion, there was some talk of renaming nodes/relation.h to avoid confusion with the new access/relation.h header. I think this is a fine idea, not only because of that conflict but because "relation.h" has never made a lot of sense as the file's name. After a bit of thought, I propose "pathnodes.h" as the new name. That fits in with the other major headers in that directory (primnodes.h, parsenodes.h, plannodes.h, execnodes.h), and it seems like a reasonable summary of what's in it. Admittedly, Path nodes as such are barely a third of the file's bulk; but I don't see any equally pithy way to describe the rest of it, unless something like planner_data.h, which is pretty unmelodious. (There was some mention of trying to split relation.h into multiple files, but I fail to see any advantage in that.) Barring objections, I'm happy to go make this happen. regards, tom lane