On Wed, Jun 24, 2015 at 10:29 AM, Andres Freund <and...@anarazel.de> wrote: > On 2015-06-24 23:05:45 +0900, Fujii Masao wrote: >> INSERT ON CONFLICT DO UPDATE doesn't seem to work on the current partitioning >> mechanism. For example, in the following SQL commands, the last UPSERT >> command >> would fail with an error. The error message is > > I think that's pretty much inevitable without baking in touple routing > into the core system and supporting unique-constraints that span > partitions. In other words, I don't think this is upsert's fault.
Is the root of the problem that the trigger is called for an INSERT .. ON CONFLICT statement but it turns that into a plain INSERT? Is there any way of writing a partitioning trigger that doesn't have that defect? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
