| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: UPSERT on partition |
| Date: | 2015-06-24 14:29:15 |
| Message-ID: | 20150624142915.GB8902@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
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.
> Or we should just treat it as a limitation of UPSERT and add that document?
I think we should (IIRC there's actually already something) rather
document it as a limitation of the partitioning approach.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2015-06-24 14:30:08 | Re: Support for N synchronous standby servers - take 2 |
| Previous Message | Fujii Masao | 2015-06-24 14:05:45 | UPSERT on partition |