| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com> |
| Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Fix SET EXPRESSION for virtual columns with whole-row dependencies |
| Date: | 2026-07-08 18:20:43 |
| Message-ID: | b6759cae-2ed0-460c-9564-5c88fc7abbf9@eisentraut.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10.06.26 11:12, Chao Li wrote:
>> fter reading the other implementation in [1], I realized that I had missed the partial-index case, so I added coverage for that.
>>
>> I am still sending an updated version of this patch because my implementation is different from the one in [1]. I would like people to compare the two approaches and decide which direction is better.
>>
>> [1]https://postgr.es/m/
>> CAJTYsWXOkyeDVbzymWc9sKrq7Y_MUv6XJXN4H9GfsBOPd3NJ+w(at)mail(dot)gmail(dot)com
>>
>> Best regards,
>> --
>> Chao Li (Evan)
>> HighGo Software Co., Ltd.
>> https://www.highgo.com/
>>
>>
> Oops! Forgot the attachment. Here comes it.
This has been addressed via the patch in the other thread.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2026-07-08 18:32:06 | Re: SPLIT/MERGE use of is_internal=true |
| Previous Message | Peter Eisentraut | 2026-07-08 18:15:54 | Re: [PATCH] Rebuild CHECK constraints after generated column SET EXPRESSION |