From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Unique indexes & constraints on partitioned tables |
Date: | 2017-12-25 21:33:53 |
Message-ID: | 20171225213353.oy3umayus3nay7wa@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Amit Langote wrote:
> Have you considered what happens when ON CONFLICT code tries to depend on
> such an index (a partitioned unique index)?
Not yet, but it was on my list of things to fix. Thanks for working on
it -- I'll be reviewing this soon.
> +create table parted_conflict_test_2 partition of parted_conflict_test for values in (2);
> +create unique index on parted_conflict_test (a);
> +insert into parted_conflict_test values (1, 'a') on conflict (a) do nothing;
> +insert into parted_conflict_test values (1, 'b') on conflict (a) do update set b = excluded.b;
> +insert into parted_conflict_test values (1, 'b') on conflict (a) do update set b = excluded.b where parted_conflict_test.b = 'a';
> +select * from parted_conflict_test;
> + a | b
> +---+---
> + 1 | b
> +(1 row)
sweet.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Rijkers | 2017-12-25 22:08:43 | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |
Previous Message | Tomas Vondra | 2017-12-25 17:40:56 | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |