mirrors/pgloader
1
0
Fork 0
mirror of https://github.com/dimitri/pgloader.git synced 2026-05-04 18:36:12 +02:00
Code Issues Projects Releases Wiki Activity

Don't catch all and any errors for retrying batches.

Browse Source 
In particular a non existing table or column shouldn't be considered as
an error we can just retry upon receiving.
This commit is contained in:
Dimitri Fontaine 2014-07-21 15:38:53 +02:00
parent a090f2fe3d
commit 3b2119cae4
1 changed files with 10 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
src/pgsql/pgsql.lisp
View File

@ -29,7 +29,11 @@
;; If PostgreSQL signals a data error, process the batch by isolating
;; erroneous data away and retrying the rest.
(cl-postgres-error::database-error (condition)
((or
cl-postgres-error::data-exception
cl-postgres-error::integrity-violation
cl-postgres-error::insufficient-resources
cl-postgres-error::program-limit-exceeded) (condition)
(retry-batch table-name columns batch batch-rows condition))))
;;;
@ -194,7 +198,11 @@
(incf current-batch-pos current-batch-rows))))
;; the batch didn't make it, prepare error handling for next turn
(cl-postgres-error::database-error (next-error-in-batch)
((or
cl-postgres-error::data-exception
cl-postgres-error::integrity-violation
cl-postgres-error::insufficient-resources
cl-postgres-error::program-limit-exceeded) (next-error-in-batch)
(setf condition next-error-in-batch