From: | Leandro Guimarães <leo(dot)guimaraes(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Copy Bulk Ignore Duplicated |
Date: | 2019-06-17 17:04:11 |
Message-ID: | CAJV35FP_Te2Qw6_TJF7CMCp9O_sE4aOi-dfFaQBN93rcsavN4Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Adrian,
Yes, that's the problem!
I'm testing now the pg_bulkload but I'm facing some issues to install it
on Postgresql 9.4.
Leandro Guimarães
On Mon, Jun 17, 2019 at 1:22 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> 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 | Andres Freund | 2019-06-17 17:43:34 | Re: checkpoints taking much longer than expected |
Previous Message | Adrian Klaver | 2019-06-17 17:01:14 | Re: Copy Bulk Ignore Duplicated |