| From: | jian he <jian(dot)universality(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure |
| Date: | 2025-06-30 01:47:31 |
| Message-ID: | CACJufxGKJtGNRRSXfwMW9SqVOPEMdP17BJ7DsBf=tNsv9pWU9g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Jun 30, 2025 at 1:32 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> I wrote:
> > jian he <jian(dot)universality(at)gmail(dot)com> writes:
> >> we can change to
> >> if (relid != tab->relid)
> >> LockRelationOid(relid, AccessExclusiveLock);
> >> obviously, the comments need to be updated.
>
> > Yeah, I came to the same conclusion after studying it for awhile.
>
This issue also applies to tab->changedStatisticsOids
and tab->changedIndexOids in ATPostAlterTypeCleanup.
drop table if exists t1,t2;
CREATE TABLE t1(a int);
CREATE TABLE t2(b t1);
CREATE STATISTICS XXX ON ((b).a is not null) FROM t2;
ALTER TABLE t1 ALTER COLUMN a TYPE numeric;
drop table if exists t1,t2;
CREATE TABLE t1(a int);
CREATE TABLE t2(b t1);
CREATE INDEX XXX ON t2(((b).a));
ALTER TABLE t1 ALTER COLUMN a TYPE numeric;
We likely need to do the same as well.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-06-30 02:23:30 | Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure |
| Previous Message | Tom Lane | 2025-06-29 17:32:40 | Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure |