Skip to content

[*] document NULL schedule behavior, fixes #833 - #834

Merged
pashagolub merged 2 commits into
cybertec-postgresql:masterfrom
robe2:runat_null_behavior_doc
Aug 28, 2026
Merged

[*] document NULL schedule behavior, fixes #833#834
pashagolub merged 2 commits into
cybertec-postgresql:masterfrom
robe2:runat_null_behavior_doc

Conversation

@robe2

@robe2 robe2 commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

If the run_at is set to NULL it is the same
as setting to run every minute

Closes #833

robe2 and others added 2 commits August 28, 2026 11:25
If the run_at is set to NULL it is the same
as setting to run every minute

Closes cybertec-postgresql#833
@pashagolub pashagolub changed the title NOTE in docs everywhere that is relevant NULL schedule is same as run every minute [*] document NULL schedule behavior, fixes #833 Aug 28, 2026
@pashagolub pashagolub self-assigned this Aug 28, 2026
@pashagolub pashagolub added the documentation Good for newcomers label Aug 28, 2026
@pashagolub
pashagolub merged commit 91817d2 into cybertec-postgresql:master Aug 28, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Good for newcomers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

run_at allows null and null is treated as run every minute

2 participants