Date: Tue, 8 Sep 2020 18:37:29 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, exclusion@gmail.com,
	pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16577: Segfault on altering a table located in a dropped
 tablespace
Message-ID: <20200908213729.GA14993@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20200908074522.GG19261@paquier.xyz>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On 2020-Sep-08, Michael Paquier wrote:

> On Tue, Aug 11, 2020 at 04:04:07PM +0900, Michael Paquier wrote:
> > Hmm.  Creating a file for partitioned table would be a completely new
> > thing as well.  heap_create() has never created a file for partitioned
> > tables since 10 so this could open to a new class of bugs.
> 
> This thread has stalled for a couple of weeks now, and I would tend to
> take the path where we'd basically revert 8725958 and ca41030.  That's
> too late for v13 to do anything about that.  But not for 14.  Any
> opinions?

Well, naturally I oppose this idea.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services