Wiki documentation scheduling logic pg_cron extension #902
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
No milestone
No project
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#902
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Wiki documentation scheduling logic reasoning for using pg_cron extension
Issue research #740
Research wiki: https://git.webug.se/Andras/BoundlessFlowCampus2K/wiki/Scheduled-Database-tasks
Basically copy-pasted the research done in issue #740, but rewrote the conclusion
The wiki page is clear and easy to follow.
It explains the two main options well.
The advantages and disadvantages of both approaches are understandable, the conclusion clearly states the chosen direction.
Things to improve:
Overall the decision is understandable.
Updated wiki in line with review