Is this normal pgwatch behaviour or is there additional configuration required?

[ME17FD]

I'm new to pgwatch, i installed the latest version for the moment 4.0.0, I built and deployed using docker, at first the instance wouldn't run due to postgres-standby having issues connection to main postgres.

Apart from some duplicating graphs that work in one place but don't in the other (pgwatch(postgres) vs pgwatch(prometheus) )
the pgwatch logs and postgres instance logs are full of errors

2025-10-02 10:16:30.967 [ERROR] [sink:postgres] [db:pgwatch_metrics] [sql:select * from admin.ensure_partition_metric_dbname_time($1, $2, $3)] [args:[instance_up ***2025-10-02 10:16:28.046309996 +0000 UTC]] [err:ERROR: relation "subpartitions.instance_up_***" does not exist (SQLSTATE 42P01)] [pid:1788] [time:8.135013ms] Query

2025-10-02 10:16:31.137 [ERROR] ERROR: relation "subpartitions.instance_up_***" does not exist (SQLSTATE 42P01)

2025-10-02 10:16:31.139 [ERROR] [columnNames:[time dbname data tag_data]] [err:ERROR: no partition of relation "instance_up" found for row (SQLSTATE 23514)] [pid:1788] [tableName:[instance_up]] [time:2.004374ms] CopyFrom

2025-10-02 10:33:21.815 [ERROR] [columnNames:[time dbname data tag_data]] [err:ERROR: no partition of relation "wal" found for row (SQLSTATE 23514)] [pid:2783] [tableName:[wal]] [time:1.191554ms] CopyFrom
....

Also some different behavior between dockerised monitored postgres vs an installed one on a Vm like not recognizing the version

[pashagolub]

Your deployment is corrupted. Please delete everything and redeploy again.

[ME17FD]

That was the first thing i did, repulling from github and rebuilding after deleteing the old containers, images and volumes

[ME17FD]

It might be worth mentioning that i did change the postgres port to be exposed on my machine on 5434

[pashagolub]

From your log I see the measurement database is corrupted and is missing critical tables.

Without seeing exact changes you applied, it's impossible to tell for sure what went wrong