Re: [PATCH] no table rewrite when set column type to constrained domain

From: solai v <solai(dot)cdac(at)gmail(dot)com>
To: jian he <jian(dot)universality(at)gmail(dot)com>
Cc: Viktor Holmberg <v(at)viktorh(dot)net>, Aditya Gollamudi <adigollamudi(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] no table rewrite when set column type to constrained domain
Date: 2026-05-14 09:18:12
Message-ID: CAF0whufpPijuCu=Lhqtca7U-Wio4gAejn7wyL6h+av1WPpBOGg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,
I tested the latest v6 patch on current master with a few different
scenarios.For the simple int to constrained-domain type change
case,the scan-only patch was used and the relfilenode stayed unchanged
before and after ALTER TABLE ,so the rewrite was avoided as expected.
I also tried USING expression cases,invalid domain values,and NULL
values.The behavior looked correct in those cases as well.
I tested with both small tables and a 1M row table.

Regards,
Solai

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2026-05-14 09:25:27 Re: Proposal: Conflict log history table for Logical Replication
Previous Message Etsuro Fujita 2026-05-14 08:57:41 Re: Fix array-element quoting in postgres_fdw import statistics