Re: BUG #16577: Segfault on altering a table located in a dropped tablespace - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #16577: Segfault on altering a table located in a dropped tablespace
Date
Msg-id 20200909124634.GC2743@paquier.xyz
Whole thread Raw
In response to Re: BUG #16577: Segfault on altering a table located in a dropped tablespace  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
List pgsql-bugs
On Wed, Sep 09, 2020 at 01:55:53AM +0200, Tomas Vondra wrote:
> Would it actually solve the issue? ISTM we'd still have to expect cases
> with partitioned tables without storage, so presumably we'd have to do
> something else ...

I am not sure what you mean here.  If we don't keep anymore references
to tablespace OIDs in pg_class for partitioned tables, meaning that we
don't leave anything dangling if the tablespace is dropped without any
files in its location, how could that be a problem?
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Markus Wanner
Date:
Subject: Re: invalid alloc size error possible in shm_mq
Next
From: PG Bug reporting form
Date:
Subject: BUG #16611: devel package installation issue.When tried to installed the PostgreSQL 11.0 version ecpg not get