| From: | Steve Midgley <science(at)misuse(dot)org> |
|---|---|
| To: | Inzamam Shafiq <inzamam(dot)shafiq(at)hotmail(dot)com> |
| Cc: | "pgsql-sql(at)lists(dot)postgresql(dot)org" <pgsql-sql(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ON CONFLICT clause NOT working on Partition Table PostgreSQL 12 |
| Date: | 2022-09-15 23:09:01 |
| Message-ID: | CAJexoS+F37aQStLD4chj51EhtLyUWFNTtC4Vduq4XqR_bFwYCQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Thu, Sep 15, 2022 at 6:32 PM Inzamam Shafiq <inzamam(dot)shafiq(at)hotmail(dot)com>
wrote:
>
> Hi Team,
>
> I have a partitioned table in postgresql12 and the unique constraint is
> applied on the child tables, when I use ON CONFLICT clause it returned an
> error "duplicate key value violates unique constraint "..."", I tried to
> replicate the scenario on a test table and created a unique index on
> partition column and the unique column but when I try to insert data it
> again return the same error.
>
> This works successfully when I directly insert data in the child table.
>
> What could be the way forward to get this work on parent table?
>
Please send DDL, sample data (ideally as inserts), and the sql statement
that causes the error. Given your description of the problem, I think if
you do that, you'll find people on this list solve the issue very quickly
for you. Without that, it's hard to diagnose, at least for me.
Best,
Steve
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Inzamam Shafiq | 2022-09-16 05:49:43 | Re: ON CONFLICT clause NOT working on Partition Table PostgreSQL 12 |
| Previous Message | Inzamam Shafiq | 2022-09-15 17:31:47 | ON CONFLICT clause NOT working on Partition Table PostgreSQL 12 |