Re: Allow ON CONFLICT DO UPDATE to return EXCLUDED values - Mailing list pgsql-hackers

From Dean Rasheed
Subject Re: Allow ON CONFLICT DO UPDATE to return EXCLUDED values
Date
Msg-id CAEZATCVwvG6QdnH3HhRfaL7=rvjq+B1Qj=XbtYuYu7ALxbX7Ew@mail.gmail.com
Whole thread Raw
In response to Re: Allow ON CONFLICT DO UPDATE to return EXCLUDED values  (Jim Jones <jim.jones@uni-muenster.de>)
Responses Re: Allow ON CONFLICT DO UPDATE to return EXCLUDED values
List pgsql-hackers
On Mon, 7 Jul 2025 at 11:38, Jim Jones <jim.jones@uni-muenster.de> wrote:
>
> I'm wondering if the current behaviour with DEFAULT columns should be
> mentioned in the docs.

Hmm, perhaps. On the INSERT page, under "conflict_action", we currently say

    Note that the effects of all per-row BEFORE INSERT triggers are
    reflected in excluded values, since those effects may have
    contributed to the row being excluded from insertion.

perhaps that should say

    Note that any values that were supplied by defaults, as well as
    the effects of all per-row BEFORE INSERT triggers are reflected
    in excluded values, since that may have contributed to the row
    being excluded from insertion.

Regards,
Dean



pgsql-hackers by date:

Previous
From: Dean Rasheed
Date:
Subject: Re: Fix replica identity checks for MERGE command on published table.
Next
From: Tom Lane
Date:
Subject: Re: A recent message added to pg_upgade