Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eGa5Y-0007HB-Q7 for pgsql-committers@arkaria.postgresql.org; Mon, 20 Nov 2017 00:37:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eGa5X-0005Y8-I8 for pgsql-committers@arkaria.postgresql.org; Mon, 20 Nov 2017 00:37:27 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eGa5X-0005Xy-1n for pgsql-committers@lists.postgresql.org; Mon, 20 Nov 2017 00:37:27 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eGa5U-0003Am-3Y for pgsql-committers@postgresql.org; Mon, 20 Nov 2017 00:37:25 +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 vAK0bIjF006918; Sun, 19 Nov 2017 19:37:18 -0500 From: Tom Lane To: Andres Freund cc: Thomas Munro , pgsql-committers Subject: Re: pgsql: Remove BufFile's isTemp flag. In-reply-to: <20171120000615.36f32ayw67xyy3h6@alap3.anarazel.de> References: <23339.1510887494@sss.pgh.pa.us> <20171117031149.hslkxis732hkjuog@alap3.anarazel.de> <24110.1510888651@sss.pgh.pa.us> <32216.1510935834@sss.pgh.pa.us> <20171117175811.qgrs75pgyhl42kgr@alap3.anarazel.de> <31532.1511128836@sss.pgh.pa.us> <20171120000615.36f32ayw67xyy3h6@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Sun, 19 Nov 2017 16:06:15 -0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <6916.1511138238.1@sss.pgh.pa.us> Date: Sun, 19 Nov 2017 19:37:18 -0500 Message-ID: <6917.1511138238@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Andres Freund writes: > On 2017-11-19 17:00:36 -0500, Tom Lane wrote: >> No, but if you're concerned about it, we could maintain API compatibility >> for extensions with something like >> #define BufFileCreateTemp(interXact) BufFileCreate(interXact) > I don't really see a point in doing this renaming in the first > place. It's not like the Temp suffix has become inaccurate. I'd perhaps > not add it in the green field, but I don't see a need to change an > existing function name. If anything it seems confusing because you'd > miss something when trivially searching the history / comparing > branches. Well, that's a fair point about history, but the reason I no longer want the Temp suffix is that it implies that there's such a thing as a non-temp BufFile. I think that's misleading if we've cut off any vestige of support for it. Anybody else have an opinion? regards, tom lane