[Bug]: duplicate key value violates unique constraint "bgw_job_stat_history_pkey" since upgrading to 2.18.2

[splitice]

What type of bug is this?

Unexpected error

What subsystems and features are affected?

Background worker

What happened?

Regular messages:

 main  [2654342.733071] postgresql[17256]: 2025-03-12 04:30:36.168 UTC [17256] ERROR:  duplicate key value violates unique constraint "bgw_job_stat_history_pkey"
 main  [2654342.735028] postgresql[17256]: 2025-03-12 04:30:36.168 UTC [17256] DETAIL:  Key (id)=(11258512) already exists.
 main  [2654342.742490] postgresql[161]: 2025-03-12 04:30:36.179 UTC [161] LOG:  background worker "TimescaleDB Background Worker Scheduler" (PID 17256) exited with exit code 1

Background jobs stop running until restart of postgresql, eventually problem returns.

TimescaleDB version affected

2.18.2

PostgreSQL version used

14.15

What operating system did you use?

Debian

What installation method did you use?

Source

What platform did you run on?

Other

Relevant log output and stack trace

How can we reproduce the bug?

That I am not sure, we have seen this on every system since upgrading.

Our systems are armv7's if thats relevant.

[akuzm]

Might be related to the duplicate job issue: #7281

[splitice]

@akuzm potentially.

Our previous timescaledb version was 2.9.3 which did not experience it. Unfortunately thats a large bisection.