Re: BUG #17409: Unable to alter data type of clustered column which is referenced by foreign key
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Japin Li <japinli@hotmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, holly.roberts@starlingbank.com,
peter@eisentraut.org, pgsql-bugs@lists.postgresql.org
Date: 2022-03-11T17:37:17Z
Lists: pgsql-bugs
I wrote: > ... The old behavior is what > ATExecAlterColumnType wants, I judge. As this stands, we will > rebuild indexes that don't need to be rebuilt, and indeed might > be on other tables altogether from the one that is being modified > (which opens all sorts of potential locking problems). Oh, well, not so much: regression=# create table atref (p1 int constraint pk_atref primary key); CREATE TABLE regression=# create table attbl (c1 int, constraint fk_atref foreign key (c1) references atref(p1)); CREATE TABLE regression=# cluster atref using pk_atref; CLUSTER regression=# alter table attbl alter column c1 set data type bigint; ERROR: "pk_atref" is not an index for table "attbl" Still, that's just as unpleasant as the originally-reported case. (I've not figured out yet why the "cluster" step is required to make this repro work.) regards, tom lane
Commits
-
Restore the previous semantics of get_constraint_index().
- 641f3dffcdf1 15.0 landed
- 8dcd1c3564f0 14.3 landed
-
Change get_constraint_index() to use pg_constraint.conindid
- 8b069ef5dca9 14.0 cited