pgloader
pgloader copied to clipboard
The assertion (NOT #1=(NULL PGLOADER::FUNC)) failed with #1# = T.
This very simple usage of pgsql --> pgsql should just work but it gives this cryptic error. I don't even know where to start. In future I'll be using it for MySQL --> pgsql but I'm testing pgsql --> pgsql first before I start using it on a live database.
root@32a4bbdda0cf:/# pgloader 'pgsql://srcusername:******@srchost-pg:5432/srcdbname' 'pgsql://dstusername:******@desthost-pg:5432/dstdbname'
KABOOM!
FATAL error: The assertion (NOT #1=(NULL PGLOADER::FUNC)) failed with #1# = T.
An unhandled error condition has been signalled:
The assertion (NOT (NULL PGLOADER::FUNC)) failed with (NULL PGLOADER::FUNC)
= T.
2022-08-09T22:18:39.017000Z LOG pgloader version "3.6.3~devel"
What I am doing here?
The assertion (NOT #1=(NULL PGLOADER::FUNC)) failed with #1# = T.
root@32a4bbdda0cf:/# pgloader --debug 'pgsql://srcusername:******@srchost-pg:5432/srcdbname' 'pgsql://dstusername:******@desthost-pg:5432/dstdbname'
pgloader version 3.6.3~devel
compiled with SBCL 1.4.16.debian
sb-impl::*default-external-format* :ANSI_X3.4-1968
tmpdir: #P"/tmp/pgloader/"
KABOOM!
FATAL error: The assertion (NOT #1=(NULL PGLOADER::FUNC)) failed with #1# = T.
Date/time: 2022-08-09-22:19!
An unhandled error condition has been signalled:
The assertion (NOT (NULL PGLOADER::FUNC)) failed with (NULL PGLOADER::FUNC)
= T.
Backtrace for: #<SB-THREAD:THREAD "main thread" RUNNING {10006385B3}>
0: (TRIVIAL-BACKTRACE:PRINT-BACKTRACE-TO-STREAM #<SB-IMPL::STRING-OUTPUT-STREAM {1005ECC8C3}>)
1: (TRIVIAL-BACKTRACE:PRINT-BACKTRACE #<SIMPLE-ERROR "~@<The assertion ~S failed~:[.~:; ~
with ~:*~{~{~S = ~S~}~^, ~}.~]~:@>" {1005ECC713}> :OUTPUT NIL :IF-EXISTS :APPEND :VERBOSE NIL)
2: ((FLET "H0" :IN PGLOADER::MAIN) #<SIMPLE-ERROR "~@<The assertion ~S failed~:[.~:; ~
with ~:*~{~{~S = ~S~}~^, ~}.~]~:@>" {1005ECC713}>)
3: (SB-KERNEL::%SIGNAL #<SIMPLE-ERROR "~@<The assertion ~S failed~:[.~:; ~
with ~:*~{~{~S = ~S~}~^, ~}.~]~:@>" {1005ECC713}>)
4: (ERROR #<SIMPLE-ERROR "~@<The assertion ~S failed~:[.~:; ~
with ~:*~{~{~S = ~S~}~^, ~}.~]~:@>" {1005ECC713}>)
5: (SB-KERNEL:WITH-SIMPLE-CONDITION-RESTARTS ERROR NIL #<SIMPLE-ERROR "~@<The assertion ~S failed~:[.~:; ~
with ~:*~{~{~S = ~S~}~^, ~}.~]~:@>" {1005ECC713}>)
6: (SB-KERNEL:ASSERT-ERROR (NOT (NULL PGLOADER::FUNC)) (((NULL PGLOADER::FUNC) T)) NIL NIL)
7: (PGLOADER::LISP-CODE-FOR-LOADING :FROM #<PGLOADER.PGSQL:PGSQL-CONNECTION pgsql://srcusername@srchost-pg:5432/srcdbname {1005EC1A53}> :INTO #<PGLOADER.PGSQL:PGSQL-CONNECTION pgsql://dstusername@desthost-pg:5432/dstdbname {1005ECA663}> :ENCODING :UTF-8 :FIELDS NIL :TARGET-TABLE-NAME NIL :OPTIONS NIL :GUCS NIL :CASTS NIL :BEFORE NIL :AFTER NIL)
8: (PGLOADER:LOAD-DATA :FROM #<PGLOADER.PGSQL:PGSQL-CONNECTION pgsql://srcusername@srchost-pg:5432/srcdbname {1005EC1A53}> :INTO #<PGLOADER.PGSQL:PGSQL-CONNECTION pgsql://dstusername@desthost-pg:5432/dstdbname {1005ECA663}> :ENCODING :UTF-8 :FIELDS NIL :TARGET-TABLE-NAME NIL :OPTIONS NIL :GUCS NIL :CASTS NIL :BEFORE NIL :AFTER NIL :START-LOGGER NIL :FLUSH-SUMMARY T)
9: (PGLOADER.MONITOR::CALL-WITH-MONITOR #<CLOSURE (LAMBDA NIL :IN PGLOADER::MAIN) {1005AF492B}>)
10: (PGLOADER::MAIN ("pgloader" "--debug" "pgsql://srcusername:******@srchost-pg:5432/srcdbname" "pgsql://dstusername:******@desthost-pg:5432/dstdbname"))
11: ((FLET SB-UNIX::BODY :IN SAVE-LISP-AND-DIE))
12: ((FLET "WITHOUT-INTERRUPTS-BODY-14" :IN SAVE-LISP-AND-DIE))
13: ((LABELS SB-IMPL::RESTART-LISP :IN SAVE-LISP-AND-DIE))
2022-08-09T22:19:13.011000Z NOTICE Starting pgloader, log system is ready.
2022-08-09T22:19:13.021000Z LOG pgloader version "3.6.3~devel"
2022-08-09T22:19:13.022000Z DEBUG LOAD DATA FROM #<PGLOADER.PGSQL:PGSQL-CONNECTION pgsql://srcusername@srchost-pg:5432/srcdbname {1005EC1A53}>
What I am doing here?
The assertion (NOT #1=(NULL PGLOADER::FUNC)) failed with #1# = T.
-
[x] pgloader --version
pgloader version "3.6.3~devel" compiled with SBCL 1.4.16.debian
-
[x] did you test a fresh compile from the source tree?
No. I'm using the image
dimitri/pgloader:latest
-
[x] did you search for other similar issues?
Yes. Many times. There are only two related issues and neither of them contain a fix. One says there's a fix but refers to itself from 2020.