Re: Copy Bulk Ignore Duplicated
От | Adrian Klaver |
---|---|
Тема | Re: Copy Bulk Ignore Duplicated |
Дата | |
Msg-id | 5380793b-0380-f494-c7a4-488770df3a3e@aklaver.com обсуждение исходный текст |
Ответ на | Copy Bulk Ignore Duplicated (Leandro Guimarães <leo.guimaraes@gmail.com>) |
Ответы |
Re: Copy Bulk Ignore Duplicated
Re: Copy Bulk Ignore Duplicated |
Список | 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.klaver@aklaver.com
В списке pgsql-general по дате отправления: