citusdata / citusdata/pg_cron

When hour field is set, then rule does not run

Open
#216 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
3.9k
Forks
260
Avg merge
5d 5h
Merged PRs (30d)
1

Description

A picture is worth a thousand words.
![image](https://user-images.githubusercontent.com/94073981/202764053-2123be4e-91a4-4b3e-8723-99cad78fdcb2.png)
![image](https://user-images.githubusercontent.com/94073981/202765867-edef85e7-b733-451b-9508-7283a9fe2afa.png)

at this moment I have just verified that there is a bug with pg_cron (all versions) where it is not possible to execute a pg_cron rule when the field corresponding to the time is filled with a constant value (Ex. 09 13 * * * ), however, if the value contains an asterisk, then it will work (Ex. 09 * * * *)

Evidence can be seen in the images above. Therefore, I request a solution to this problem.

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no source file, test, or entry point. Start by reproducing the reported behavior with the two cron expressions shown in the issue, then trace how pg_cron parses and schedules an expression with a constant hour. Done means the constant-hour rule executes as expected and the behavior is covered by a regression test.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, postgresql
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.