Replies: 1 comment 8 replies
-
|
Hello. Would you please provide a definition of the chain? Please set |
Beta Was this translation helpful? Give feedback.
-
|
Is it |
Beta Was this translation helpful? Give feedback.
-
CREATE OR REPLACE FUNCTION sleepy_func(text)
RETURNS void LANGUAGE plpgsql AS
$BODY$
BEGIN
RAISE NOTICE 'Sleeping for 15 sec in %', $1;
PERFORM pg_sleep_for('15 seconds');
RAISE NOTICE 'Waking up in %', $1;
END;
$BODY$;
SELECT timetable.add_job(
job_name => 'exclusive sleepy task every 5 sec',
job_schedule => '@every 5 seconds',
job_command => 'SELECT sleepy_func($1)',
job_parameters => '[ "Configuration EVERY 10sec" ]'::jsonb,
job_kind => 'SQL'::timetable.command_kind,
job_max_instances => 1,
job_live => TRUE,
job_exclusive => FALSE
) I tried this approach but cannot reproduce the error. Can you show the full |
Beta Was this translation helpful? Give feedback.
-
No, I used refresh without concurrently |
Beta Was this translation helpful? Give feedback.
-
With sleepy_func I also can't reproduce it. Here full timetable.execution_log
|
Beta Was this translation helpful? Give feedback.
-
|
Ough. Mystery. Would you please run the session with |
Beta Was this translation helpful? Give feedback.
-
Hi.
I have ONE chain with ONE task that run every 5 seconds.
But sometimes when task runs more then 5 seconds new task starts.
And this leads to errors in the execution of the procedure called in the task.
From timetable.execution_log:
From timetable.log:
Can you tell me how to avoid parallel task launches?
Beta Was this translation helpful? Give feedback.
All reactions