Re: bug when apply fast default mechanism for adding new column over domain with default value

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tender Wang <tndrwang(at)gmail(dot)com>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: bug when apply fast default mechanism for adding new column over domain with default value
Date: 2025-04-02 15:15:41
Message-ID: 876696.1743606941@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tender Wang <tndrwang(at)gmail(dot)com> writes:
> So let's add CommandCounterIncrement() after calling StoreAttrMissingVal().

Pushed with minor editorialization. I thought for a bit about whether
the CCI call should be inside StoreAttrMissingVal; but its cohorts in
heap.c don't do their own CCI calls, so this way seems the least
surprising.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2025-04-02 15:19:58 Re: in BeginCopyTo make materialized view using COPY TO instead of COPY (query).
Previous Message Bertrand Drouvot 2025-04-02 15:00:52 Re: Fix 035_standby_logical_decoding.pl race conditions