From: Michael Paquier <michael@paquier.xyz>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: exclusion@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16577: Segfault on altering a table located in a dropped tablespace
Date: Wed, 28 Oct 2020 14:18:21 +0900
Message-ID: <20201028051821.GI28445@paquier.xyz> (raw)
In-Reply-To: <20201015151959.GA6823@alvherre.pgsql>
References: <20200908235553.7tbd6xjvnohv2xel@development>
<20201015151959.GA6823@alvherre.pgsql>
On Thu, Oct 15, 2020 at 12:19:59PM -0300, Alvaro Herrera wrote:
> It just dawned on me that a way to fix this is to use a pg_shdepend
> entry to protect the tablespace from being dropped.
Haven't thought of that approach, good idea! That would not be
backpatchable but that would be a solution that does not require
creating files where we don't need them. Did you begin to look at
that?
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: michael@paquier.xyz, alvherre@alvh.no-ip.org, tomas.vondra@2ndquadrant.com, 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
In-Reply-To: <20201028051821.GI28445@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox