| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Leandro Guimarães <leo(dot)guimaraes(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Copy Bulk Ignore Duplicated |
| Date: | 2019-06-17 16:22:21 |
| Message-ID: | 5380793b-0380-f494-c7a4-488770df3a3e@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 6/17/19 9:06 AM, Leandro Guimarães wrote:
Please reply to list also.
Ccing list.
> Ugh My bad again.
>
> They are UNIQUE:
> CONSTRAINT unique_const_value_20190501_45 UNIQUE (customer_id,
> date_time, indicator_id, element_id),
>
> I've made a mistake typing "check constraint" before because these are
> partitioned tables and I have the CHECK CONSTRAINT to partition.
>
> Is that clear?
Yes.
To get back to the original issue, the problem is that when you COPY in
new data you may get rows that conflict on the above UNIQUE constraint,
correct?
>
> Thanks for your patience!
> Leandro Guimarães
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2019-06-17 17:01:14 | Re: Copy Bulk Ignore Duplicated |
| Previous Message | Adrian Klaver | 2019-06-17 16:06:34 | Re: psql timeout option |