Problem on migrating from 4.1.0 to 5.0.0

[clmntpllr]

After installing the 5.0.0 rpm package (Rhel 8.10), I launched the command pgwatch config upgrade
and got the error :

2026-03-04 09:32:04.095 [ERROR] [callstack:goroutine 1 [running]:
runtime/debug.Stack()
        /opt/hostedtoolcache/go/1.26.0/x64/src/runtime/debug/stack.go:26 +0x5e
main.main.func1()
        /home/runner/work/pgwatch/pgwatch/cmd/pgwatch/main.go:50 +0xc5
panic({0xed6520?, 0x2f92cf4a6d20?})
        /opt/hostedtoolcache/go/1.26.0/x64/src/runtime/panic.go:860 +0x13a
github.com/cybertec-postgresql/pgwatch/v5/internal/cmdopts.(*ConfigUpgradeCommand).Execute.func1({0x2f92cf05805b, 0x3f}, 0x2f92cf2c1b20)
        /home/runner/work/pgwatch/pgwatch/internal/cmdopts/cmdconfig.go:110 +0x159
github.com/cybertec-postgresql/pgwatch/v5/internal/cmdopts.(*ConfigUpgradeCommand).Execute(0x1bc7070?, {0xeadc80?, 0x7f96a4b2da01?, 0x7f96eb7e04e8?})
        /home/runner/work/pgwatch/pgwatch/internal/cmdopts/cmdconfig.go:114 +0xad
github.com/jessevdk/go-flags.(*Parser).ParseArgs(0x2f92cf3bc070, {0x2f92cf050550, 0x2, 0x2})
        /home/runner/go/pkg/mod/github.com/jessevdk/go-flags@v1.6.1/parser.go:339 +0xacc
github.com/jessevdk/go-flags.(*Parser).Parse(...)
        /home/runner/go/pkg/mod/github.com/jessevdk/go-flags@v1.6.1/parser.go:195
github.com/cybertec-postgresql/pgwatch/v5/internal/cmdopts.New({0x12106e0, 0x2f92cf014040})
        /home/runner/work/pgwatch/pgwatch/internal/cmdopts/cmdoptions.go:76 +0xd9
main.main()
        /home/runner/work/pgwatch/pgwatch/cmd/pgwatch/main.go:59 +0xd7
] interface conversion: *sources.dbSourcesReaderWriter is not db.Migrator: missing method Migrate

The pgwatch.log ask me to lauch that command : {"level":"error","msg":"sink database schema is outdated, please run migrations using ``pgwatch config upgrade`` command","time":"2026-03-04T09:31:03+01:00"}

Thanks for your help !
Regards
Clément

[0xgouda]

Ouch, that's probably a bug related to handling pg sources, thanks for pointing it out.

The good news is that there aren't any migrations for sources from v4.1.0 to v5.0.0, so run the config upgrade command with only --sink and --metrics specified as a workaround to get you up and running.

will work on resolving the issue rn.

[clmntpllr]

Hi, thank you, it worked !

2026-03-04 10:22:12.373 [INFO] [notice:relation "migration" already exists, skipping] [severity:NOTICE] Notice received
2026-03-04 10:22:12.419 [INFO] Applying migration named '01110 Apply postgres sink schema migrations'...
2026-03-04 10:22:12.420 [INFO] Applied migration named '01110 Apply postgres sink schema migrations'
2026-03-04 10:22:12.421 [INFO] Applying migration named '01180 Apply admin functions migrations for v5'...
2026-03-04 10:22:12.439 [INFO] Applied migration named '01180 Apply admin functions migrations for v5'

[bkhomuts]

I have seen the same error, and removing PW_SOURCES environment variable helped to complete migration. Thanks for the solution!