| From: | Yan Chunlu <springrider(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: ignore duplicate key while using COPY? |
| Date: | 2011-12-22 02:12:58 |
| Message-ID: | CAOA66tFe3T=8nYtMZRAaysADqGxs_pJRqFZitVP+YsnVsbYCSQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
thanks a lot!
On Mon, Dec 19, 2011 at 10:19 PM, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>wrote:
> On Sunday, December 18, 2011 10:54:21 pm Yan Chunlu wrote:
> > I am using COPY public.table_name FROM STDIN to import data. it is
> > very efficient, but if there's any duplicate key exists, the whole
> > procedure has been stopped. is there anyway to around this?
> >
> > why does not postgresql just give a warning and continue the copy?
>
> Take a look at pgloader:
> http://pgfoundry.org/projects/pgloader/
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)gmail(dot)com
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Morton | 2011-12-22 03:57:18 | Re: Help with Multiple Cluster on same host |
| Previous Message | Adrian Klaver | 2011-12-22 01:16:08 | Re: Escaping input from COPY |