From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
---|---|
To: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Allow ON CONFLICT DO UPDATE to return EXCLUDED values |
Date: | 2025-07-07 17:52:40 |
Message-ID: | CAEZATCVwvG6QdnH3HhRfaL7=rvjq+B1Qj=XbtYuYu7ALxbX7Ew@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 7 Jul 2025 at 11:38, Jim Jones <jim(dot)jones(at)uni-muenster(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-07-07 17:52:56 | Re: A recent message added to pg_upgade |
Previous Message | Dean Rasheed | 2025-07-07 17:17:40 | Re: Fix replica identity checks for MERGE command on published table. |