Re: Problem with aborting entire transactions on error
| От | Ondrej Ivanič |
|---|---|
| Тема | Re: Problem with aborting entire transactions on error |
| Дата | |
| Msg-id | CAM6mieKn-Mb67S0TdU5SAWtwR=fTPgHsYb_nCxH9MUTNKevJgQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Problem with aborting entire transactions on error (Виктор Егоров <vyegorov@gmail.com>) |
| Список | 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 по дате отправления: