Re: BUG #19100: Different column type between partitioned table and detached pending partition table make errors - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #19100: Different column type between partitioned table and detached pending partition table make errors
Date
Msg-id 442267.1762108572@sss.pgh.pa.us
Whole thread Raw
In response to BUG #19100: Different column type between partitioned table and detached pending partition table make errors  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #19100: Different column type between partitioned table and detached pending partition table make errors
List pgsql-bugs
PG Bug reporting form <noreply@postgresql.org> writes:
> It's evident that in both error cases, the failure occurs because
> column name has different data types between the parent and the child
> table. BTW, "\d+ users_p0" error happens when
> pg_get_partition_constraintdef() is called. The root cause seems to be
> that when running:
> ```
> ALTER TABLE users ALTER COLUMN name TYPE char(10);
> ```
> on the parent table, the statement does not affect a child table that is in
> detach pending state.

Ugh.

> IMO, a detach pending child table is not affected by parent's DML or DQL,
> but should still be affected by parent's DDL.

I think it'd be far safer to refuse all forms of ALTER TABLE until the
detach is completed.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Inconsistencies around Composite Row nullness
Next
From: dqetool
Date:
Subject: Re:Re: BUG #19101: Ceil on BIGINT could lost precision in decil function