Re: bug when apply fast default mechanism for adding new column over domain with default value - Mailing list pgsql-hackers

From Tom Lane
Subject Re: bug when apply fast default mechanism for adding new column over domain with default value
Date
Msg-id 4060266.1741027118@sss.pgh.pa.us
Whole thread Raw
In response to Re: bug when apply fast default mechanism for adding new column over domain with default value  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
I wrote:
> jian he <jian.universality@gmail.com> writes:
>> within ATExecAddColumn, we can
>>     if (!missingIsNull)
>>         StoreAttrMissingVal(rel, attribute->attnum, missingval, missingIsNull);
>> to save some cycles?

> Probably not really worth it: surely that's going to be a very
> infrequent edge case.

On second thought, it is worth doing like that, not on speed
grounds but because we can make StoreAttrMissingVal simpler
by not handling the is-null case at all.

Pushed with that adjustment and some other minor polishing.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Change log level for notifying hot standby is waiting non-overflowed snapshot
Next
From: Antonin Houska
Date:
Subject: Re: why there is not VACUUM FULL CONCURRENTLY?