Fabrízio de Royes Mello 6063464f6d Fix wrong crash error message on job history
Currently while a job is running we set `pid = SchedulerPid`,
`succeed = false` and `execution_finish=NOW()` and it leads to
confusion when querying either `timescaledb_information.job_errors`
or `timescaledb_information.job_history` views showing in the
`err_message = job crash detected, see server logs`. This information
is wrong and create confusion.

Fixed it by setting `succeed=NULL` and `pid=NULL` when the scheduler
launch the job and then when the job worker start to work then set
`pid=MyProcPid` (the worker PID) meaning that the job started and
didn't finished yet, and at the end of the execution we set
`succeed=TRUE or FALSE` and the `execution_finish=NOW()` to mark the
end of the job execution. Also adjusted the views to expose the
information properly.
2025-02-11 16:42:37 -03:00
..
2024-09-04 11:29:32 +02:00
2025-02-11 10:41:16 +01:00
2024-04-04 10:39:28 -03:00
2024-10-16 13:13:34 +02:00
2023-09-28 08:14:30 +02:00