Re: BUG #16577: Segfault on altering a table located in a dropped tablespace

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16577: Segfault on altering a table located in a dropped tablespace
Date: 2020-09-08 07:45:22
Message-ID: 20200908074522.GG19261@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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?
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jehan-Guillaume de Rorthais 2020-09-08 14:15:11 Re: [BUG v13] Crash with event trigger in extension
Previous Message Michael Paquier 2020-09-08 05:27:03 Re: [BUG v13] Crash with event trigger in extension