mirrors/pgloader
1
0
Fork 0
mirror of https://github.com/dimitri/pgloader.git synced 2025-08-08 15:27:00 +02:00
Code Issues Projects Releases Wiki Activity

Be more verbose with long-running loads.

Browse Source 
Add a message every 20 batches so that the user knows it's still going on.
Also, in passing, fix some messages: present is not precise enough to decide
if the log refers to an event that is being done or starting next.
This commit is contained in:
Dimitri Fontaine 2017-08-21 16:50:16 +02:00
parent 28db6b9f13
commit c62f4279c0
3 changed files with 17 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
src/package.lisp
View File

@ -207,6 +207,7 @@
#:pgtable-initialize-reject-files
#:pgtable-secs
#:pgtable-rows
#:pgtable-start
#:pgtable-stop
#:pgtable-reject-data

2
src/sources/common/db-methods.lisp
View File

@ -135,7 +135,7 @@
;; able to benefit from the indexes. In particular avoid doing that step
;; while CREATE INDEX statements are in flight (avoid locking).
;;
(log-message :notice "Complete PostgreSQL database.")
(log-message :notice "Completing PostgreSQL database.")
(when reset-sequences
(reset-sequences (clone-connection (target-db copy)) catalog))

15
src/utils/monitor.lisp
View File

@ -238,6 +238,21 @@
:rs (update-stats-rs event)
:ws (update-stats-ws event))
;; log some kind of a “keep alive” message to the user, for
;; the sake of showing progress.
;;
;; something like one message every 20 batches should only
;; target big tables where we have to wait for a pretty long
;; time.
(when (and (update-stats-rows event)
(typep label 'pgloader.catalog:table)
(< (* 19 *copy-batch-rows*)
(mod (pgtable-rows table)
(* 20 *copy-batch-rows*))))
(log-message :notice "copy ~a: ~d rows done"
(pgloader.catalog:format-table-name label)
(pgtable-rows table)))
(when (update-stats-start event)
(log-message :debug "start ~a ~30t ~a"
(pgloader.catalog:format-table-name label)