DB errors after v9 upgrade, bug maybe

Hi,
I have automatic updates for Grafana, running on Ubuntu 18.x
DB Postgresql 9.3.
After the latest upgrade, unified alerting was applied/enabled, and i like the look of it. But… it seems to break the old stuff and I cant add new alerts either.
This is all over my logs:
Jun 22 12:38:13 XYX311AZ grafana-server[11179]: logger=ngalert t=2022-06-22T12:38:13.560555756+02:00 level=error msg=“failed to save alert state” uid=kk8ZHNq7z orgId=1 labels=“alert_rule_namespace_uid=npAduJO7k, alert_rule_uid=kk8ZHNq7z, alertname=BGP - WANRO01” state=Normal msg=“pq: syntax error at or near "ON"”

The “msg” part at the end is the key thing that is flooded in the logs.
I’ve spent plenty of time trying to work around it or find some kind of trace on how to fix this, but without any success.
Any ideas from the ones with bad ass knowledge in this area? =)

…adding logs from postgresql 9.3 logs.
2022-06-22 13:37:55 CEST ERROR: syntax error at or near “ON” at character 222
2022-06-22 13:37:55 CEST STATEMENT: INSERT INTO alert_instance (“rule_org_id”, “rule_uid”, “labels”, “labels_hash”, “current_state”, “current_reason”, “current_state_since”, “current_state_end”, “last_eval_time”) VALUES ($1, $2, $3, $4, $5, $6, $7, $8, $9) ON CONFLICT(“rule_org_id”, “rule_uid”, “labels_hash”) DO UPDATE SET “rule_org_id”=excluded.“rule_org_id”, “rule_uid”=excluded.“rule_uid”, “labels”=excluded.“labels”, “labels_hash”=excluded.“labels_hash”, “current_state”=excluded.“current_state”, “current_reason”=excluded.“current_reason”, “current_state_since”=excluded.“current_state_since”, “current_state_end”=excluded.“current_state_end”, “last_eval_time”=excluded.“last_eval_time”

//R

Also, running debug in grafana shows:
logger=ngalert uid=StFtxYj7k org=1 version=4 attempt=0 now=2022-06-22T14:14:57.157697308+02:00 t=2022-06-22T14:15:02.166260305+02:00 level=debug msg=“alert rule evaluated” results=“unsupported value type” duration=7.095106ms
logger=ngalert t=2022-06-22T14:15:02.166305105+02:00 level=debug msg=“state manager processing evaluation results” uid=StFtxYj7k resultCount=1
logger=ngalert t=2022-06-22T14:15:02.166587023+02:00 level=debug msg=“setting alert state” uid=StFtxYj7k
logger=ngalert t=2022-06-22T14:15:02.166882921+02:00 level=error msg=“failed to save alert state” uid=StFtxYj7k orgId=1 labels=“alert_rule_namespace_uid=65KpxYCnz, alert_rule_uid=StFtxYj7k, alertname=My alert, rule_uid=StFtxYj7k” state=Alerting msg=“pq: syntax error at or near "ON"”
logger=ngalert uid=StFtxYj7k org=1 version=4 attempt=0 now=2022-06-22T14:14:57.157697308+02:00 t=2022-06-22T14:15:02.166931014+02:00 level=debug msg=“no alerts to put in the notifier or to send to external Alertmanager(s)”

And yes, I see the part of unsupported value but cannot pinpoint why.