Make interactive debugging easier.

It's fair game to handle errors and issue logs instead when using the
pgloader binary image, as it distracts users a lot. That said, as a
developer the interactive debugger is very useful.

In passing install some experimental thread killing behavior in case of
errors and using on-error-stop setting (default for database migrations).

Author: dimitri

src/load/copy-data.lisp

@@ -74,13 +74,17 @@
              (incf task-count)))
 
       (lp:task-handler-bind
-          ((copy-init-error
+          (#+pgloader-image
+           (copy-init-error
             #'(lambda (condition)
-                ;; everything has been handled already
+                ;; stop the other tasks and then transfer the control
+                (log-message :log "COPY INIT ERROR")
+                (lp:kill-tasks :default)
                 (lp:invoke-transfer-error condition)))
            (on-error-stop
             #'(lambda (condition)
-                ;; everything has been handled already
+                (log-message :log "ON ERROR STOP")
+                (lp:kill-tasks :default)
                 (lp:invoke-transfer-error condition)))
            #+pgloader-image
            (error

src/utils/monitor.lisp

@@ -147,15 +147,17 @@
                       (*summary-pathname*    . ,*summary-pathname*)
                       (*sections*            . ',*sections*)))
          (kernel      (lp:make-kernel 1 :bindings bindings))
-         (lparallel:*kernel* kernel))
+         (lparallel:*kernel* kernel)
+         (lparallel:*task-category* :monitor))
 
     ;; make our kernel and channel visible from the outside
     (setf *monitoring-kernel* kernel
           *monitoring-channel* (lp:make-channel)
           *monitoring-queue*   (lq:make-queue))
 
     (lp:task-handler-bind
-        ((error
+        (#+pgloader-image
+         (error
           #'(lambda (c)
               ;; we can't log-message a monitor thread error
               (lp:invoke-transfer-error