Feedback-ID: ia2694551:Fastmail
Date: Wed, 7 Aug 2024 14:50:50 -0400
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tender Wang <tndrwang@gmail.com>
Cc: exclusion@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18541: Reattaching a partition referenced by a foreign key
 fails with an error
Message-ID: <202408071850.g7wjetpfbloe@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <202408071844.d7mzelswgpdu@alvherre.pgsql>
Archived-At: 
 <https://www.postgresql.org/message-id/202408071850.g7wjetpfbloe%40alvherre.pgsql>
Precedence: bulk

On 2024-Aug-07, Alvaro Herrera wrote:

> I think this schema is nuts.  Do you have a practical use for something
> like this?

FWIW if you try to set this up the other way around, you get a different
error:

create table t (a int primary key) partition by list (a);
create table t1 partition of t for values in (1);
alter table t add foreign key (a) references t1;
ERROR:  cannot ALTER TABLE "t1" because it is being used by active queries in this session

so I'm not bothered by the restriction in functionality.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/