From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: pgsql-committers@postgresql.org,
        Thomas Munro <thomas.munro@enterprisedb.com>
Subject: Re: pgsql: Remove BufFile's isTemp flag.
In-reply-to: <20171117175811.qgrs75pgyhl42kgr@alap3.anarazel.de>
References: <E1eFVyl-0008J1-RO@gemulon.postgresql.org>
 <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>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Fri, 17 Nov 2017 09:58:11 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <12524.1510942166.1@sss.pgh.pa.us>
Date: Fri, 17 Nov 2017 13:09:26 -0500
Message-ID: <12525.1510942166@sss.pgh.pa.us>
Precedence: bulk

Andres Freund <andres@anarazel.de> writes:
> On 2017-11-17 11:23:54 -0500, Tom Lane wrote:
>> Or maybe we should revert 11e264517.  It doesn't seem to be buying
>> much to make up for the loss of flexibility.

> There's a bunch of work adding new functionality to buffile.c
> pending. And having code paths that have been dead for 10+ years around
> and maintaining them in working order doesn't seem like a good use of
> time.

OK, if there's active work going on in the area, that's a good reason
to simplify.  But let's get rid of all vestiges of the old non-temp
semantics.

			regards, tom lane