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

From Ondrej Ivanič
Subject Re: Problem with aborting entire transactions on error
Date
Msg-id CAM6mieKn-Mb67S0TdU5SAWtwR=fTPgHsYb_nCxH9MUTNKevJgQ@mail.gmail.com
Whole thread Raw
In response to Re: Problem with aborting entire transactions on error  (Виктор Егоров <vyegorov@gmail.com>)
List pgsql-general
Hi,

On 11 December 2012 06:25, Виктор Егоров <vyegorov@gmail.com> wrote:
> On the other hand, it is possible to write "whenever sqlerror
> continue;" and this will make ORACLE to process all the statements
> inide the script, ignoring all errors. This is a general feature,
> available not only for sqlplus scripts — as mentioned, a series of 100
> INSERTs can have 5 failing ones and commit statement will result in 95
> new records..

For example, nCluster (and Greenplum) has similar feature for COPY:
page 13 "Error Logging in COPY"
http://www.pgcon.org/2009/schedule/attachments/135_PGCon%202009%20-%20Aster%20v6.pdf.

Around the same time AsterData tried to push some COPY enhancements
(error logging and partitioning):
http://archives.postgresql.org/pgsql-hackers/2009-10/msg00247.php

--
Ondrej Ivanic
(http://www.linkedin.com/in/ondrejivanic)


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Problem with aborting entire transactions on error
Next
From: Tom Lane
Date:
Subject: Re: execution plan is wrong, or the query ?