Re: [BUG] ON CONFLICT DO UPDATE SET x = EXCLUDED.<virtual-generated-column> errors or silently writes NULL

From: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
To: SATYANARAYANA NARLAPURAM <satyanarlapuram(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [BUG] ON CONFLICT DO UPDATE SET x = EXCLUDED.<virtual-generated-column> errors or silently writes NULL
Date: 2026-04-22 08:12:15
Message-ID: CAEZATCVpD24d13opa6ghuJ8y10cOqG81MVU-gZZxtG-9L4EuTw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 20 Apr 2026 at 01:55, SATYANARAYANA NARLAPURAM
<satyanarlapuram(at)gmail(dot)com> wrote:
>
>> Attached is a v2 patch doing it that way, with the same tests, which all pass.
>
> Reran the failing tests and they all passed. Additionally ran the regression tests.
> Patch looks good to me.
>

Thanks for checking. Patch pushed and back-patched to v18.

Regards,
Dean

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Arseniy Mukhin 2026-04-22 08:14:52 Re: amcheck support for BRIN indexes
Previous Message Masahiko Sawada 2026-04-22 08:02:20 Re: Fix pg_upgrade to detect invalid logical replication slots on PG19