From 5ecd03ceba21d7540db94badba2d68a9c05852e4 Mon Sep 17 00:00:00 2001 From: Dimitri Fontaine Date: Thu, 25 Jan 2018 23:53:11 +0100 Subject: [PATCH] Don't push-row a nil value. In case of a failure to pre-process or transform values in the row that as been read, we need to refrain from pushing the row into our next batch. See #726, that got hit by the recent bug in the middle of something else entirely. --- src/pg-copy/copy-rows-in-batch.lisp | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/pg-copy/copy-rows-in-batch.lisp b/src/pg-copy/copy-rows-in-batch.lisp index ee28f33..5542581 100644 --- a/src/pg-copy/copy-rows-in-batch.lisp +++ b/src/pg-copy/copy-rows-in-batch.lisp @@ -141,4 +141,5 @@ "Given a row from the queue, prepare it for the next batch." (multiple-value-bind (pg-vector-row bytes) (prepare-and-format-row copy nbcols row) - (push-row current-batch pg-vector-row bytes))) + (when pg-vector-row + (push-row current-batch pg-vector-row bytes))))