Re: Partial update on an postgres upsert violates constraint - Mailing list pgsql-general

From Kim Rose Carlsen
Subject Re: Partial update on an postgres upsert violates constraint
Date
Msg-id AM4PR0501MB261097AEABE315EC1410A623C7B30@AM4PR0501MB2610.eurprd05.prod.outlook.com
Whole thread Raw
In response to Re: Partial update on an postgres upsert violates constraint  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: Partial update on an postgres upsert violates constraint  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general

> AFAIK, EXCLUDED is only available in a trigger function:

>
https://www.postgresql.org/docs/9.5/static/trigger-definition.html
>
> You are using EXCLUDED in a regular function so it would not be found.

> Can you also show the failure for your alternate method?

From the manual
"
conflict_action
conflict_action specifies an alternative ON CONFLICT action. It can be either DO NOTHING, or a DO UPDATE clause specifying the exact details of the UPDATE action to be performed in case of a conflict. The SET and WHERE clauses in ON CONFLICT DO UPDATE have access to the existing row using the table's name (or an alias), and to rows proposed for insertion using the special excluded table. SELECT privilege is required on any column in the target table where corresponding excluded columns are read.
"

pgsql-general by date:

Previous
From: "Fran ..."
Date:
Subject: Re: Database migration to RDS issues permissions
Next
From: Adrian Klaver
Date:
Subject: Re: Partial update on an postgres upsert violates constraint