| From: | David Johnston <polobo(at)yahoo(dot)com> |
|---|---|
| To: | Zbigniew <zbigniew2011(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Problem with aborting entire transactions on error |
| Date: | 2012-12-11 14:33:39 |
| Message-ID: | B7AF2D92-5916-4B4F-A14A-DE2E2FD6FA82@yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Dec 11, 2012, at 6:48, Zbigniew <zbigniew2011(at)gmail(dot)com> wrote:
> 2012/12/11, Abel Abraham Camarillo Ojeda <acamari(at)the00z(dot)org>:
>
>> Obviously, it's not fast...
>
> Well, the problem was exactly speed-related. If not this - I could
> simply dispose of the transaction...
> --
> regards,
> Zbigniew
>
>
It seems like if you switched to the COPY API and a staging table your initial performance would be maximized and from the delta gain you can run the second transformation query. Your desired feature probably wouldn't work with copy anyway and high-performance bulk loading should use that API.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2012-12-11 15:01:26 | Re: Problem with aborting entire transactions on error |
| Previous Message | Merlin Moncure | 2012-12-11 14:31:24 | Re: Looking for cooperators |