Re: BUG #16714: INSERT ON CONFLICT DO UPDATE fails to infer constraint if it's not at top-level partition - Mailing list pgsql-bugs

From Andy S
Subject Re: BUG #16714: INSERT ON CONFLICT DO UPDATE fails to infer constraint if it's not at top-level partition
Date
Msg-id CAFAcjJNU+2Eyx_s381ADrMjcBpZKTPATYaj=cdntiGEmoByVZw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #16714: INSERT ON CONFLICT DO UPDATE fails to infer constraint if it's not at top-level partition  (Andy S <gatekeeper.mail@gmail.com>)
Responses Re: BUG #16714: INSERT ON CONFLICT DO UPDATE fails to infer constraint if it's not at top-level partition
List pgsql-bugs
Oh! What a gem I mined in sources:

branch: REL_11_STABLE
src/backend/executor/nodeModifyTable.c:
         * BEFORE ROW INSERT Triggers.
         *
         * Note: We fire BEFORE ROW TRIGGERS for every attempted insertion in an
         * INSERT ... ON CONFLICT statement.  We cannot check for constraint
         * violations before firing these triggers, because they can change the
         * values to insert.  Also, they can run arbitrary user-defined code with
         * side-effects that we can't cancel by just not inserting the tuple.
         */

Still not the place where ON CONFLICT could be validated on per-row basis?

pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: BUG #16722: PG hanging on COPY when table has close to 2^32 toasts in the table.
Next
From: PG Bug reporting form
Date:
Subject: BUG #16726: Invalid input syntax is not a useful error message