Re: bug: repeated ALTER COLUMN SET DATA TYPE corrupt check constraint - Mailing list pgsql-hackers

From jian he
Subject Re: bug: repeated ALTER COLUMN SET DATA TYPE corrupt check constraint
Date
Msg-id CACJufxECtm=EpiquvXhWKmP0x7-RNt5=qDuXJuuQkQ+6bOFXLA@mail.gmail.com
Whole thread Raw
In response to Re: bug: repeated ALTER COLUMN SET DATA TYPE corrupt check constraint  (Srinath Reddy Sadipiralla <srinath2133@gmail.com>)
List pgsql-hackers
On Sat, Dec 27, 2025 at 4:32 PM Srinath Reddy Sadipiralla
<srinath2133@gmail.com> wrote:
>>
>
> Yeah, I can easily reproduce this.
>
hi.

thinking about it more...
I tend to think it's not a bug.
because SET DATA TYPE changes the CHECK constraint definition.

>> DROP TABLE IF EXISTS main_table;
>> CREATE TABLE main_table (a int, b int, check(a = b));
>> ALTER TABLE main_table ALTER COLUMN a SET DATA TYPE numeric;
>> ALTER TABLE main_table ALTER COLUMN a SET DATA TYPE int;

At this stage, the constraint definition is no longer "a = b",
it becomes "(a::numeric = b::numeric)", which is different from "(a = b)".

sorry for the noise.



pgsql-hackers by date:

Previous
From: "cca5507"
Date:
Subject: Missing oauth_validator_libraries in variable_is_guc_list_quote()
Next
From: Laurenz Albe
Date:
Subject: Re: Get rid of "Section.N.N.N" on DOCs