Re: Problem with aborting entire transactions on error - Mailing list pgsql-general

From David Johnston
Subject Re: Problem with aborting entire transactions on error
Date
Msg-id B7AF2D92-5916-4B4F-A14A-DE2E2FD6FA82@yahoo.com
Whole thread Raw
In response to Re: Problem with aborting entire transactions on error  (Zbigniew <zbigniew2011@gmail.com>)
List pgsql-general
On Dec 11, 2012, at 6:48, Zbigniew <zbigniew2011@gmail.com> wrote:

> 2012/12/11, Abel Abraham Camarillo Ojeda <acamari@the00z.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
thedelta gain you can run the second transformation query.  Your desired feature probably wouldn't work with copy
anywayand high-performance bulk loading should use that API. 

David J.



pgsql-general by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: Looking for cooperators
Next
From: Merlin Moncure
Date:
Subject: Re: Problem with aborting entire transactions on error