Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: jian he <jian(dot)universality(at)gmail(dot)com>
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-29 17:32:40
Message-ID: 2537374.1751218360@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

Here's a patch for that. Working on back-patching it ...

regards, tom lane

Attachment Content-Type Size
fix-bug-18970.patch text/x-diff 4.2 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message jian he 2025-06-30 01:47:31 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:01:53 Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure