How to run cron jobs in Postgres without extra infrastructure
wasp.sh
wasp.sh
In other words, I want to disable all jobs for some time (for benchmarking) and then bring them back up.
Stop all active timers: ```bash sudo systemctl stop $(cat /tmp/active_timers.txt) ```
Later, restart the previously active timers: ```bash sudo systemctl start $(cat /tmp/active_timers.txt) ```
Some others:
* https://github.com/LaunchPlatform/bq
* https://github.com/cybertec-postgresql/pg_timetable
* https://github.com/pgmq/pgmq
* https://github.com/riverqueue/river
* https://github.com/oban-bg/oban
* https://github.com/pgadmin-org/pgagent
* https://github.com/citusdata/pg_cron
etc. There are plenty of options to choose from.
https://github.com/tktech/chancy
> As a rule of thumb, if you're processing less than 1000 jobs per day or your jobs are mostly lightweight operations (like sending emails or updating records), you can stick with this solution.
This seems... excessively low? Chancy is on the heavier side and happily does many millions of jobs per day. Postgres has no issue with such low throughput, even on resource constrained systems (think a $5 vps). Maybe they meant 1000 per second?
Chancy also looks pretty neat. Thanks for sharing!
Cron's name originates from Chronos, at least according to Wikipedia.
You don't need WASP for any of this, certainly not worth learning their custom DSL for it. Two of their points about how it makes it better are moot, setting queue names (one line of code) and type safety (you should be using TS already). I've not seen the value in their abstractions and indirection.
pg_cron is for pg specific cron tasks. You use pg_cron to truncate a table, compute pg views, values, aggregates, etc. Basically just running PG queries on a CRON schedule.
pg_cron itself won't run an external script for you. Like you can't do
SELECT cron.schedule('0/30 * * * *', $$ ./sendEmails.sh $$);
It works well with Supabase, I tried it, its decent but you should only use it for endpoints you trust because waiting for the request is blocking.
If you want the requests to be async you need to use pg_background extension with it
How does your library work in this regard? If my node server is down, will my scheduled tasks still execute? I notice you have a .start() method, what does that do? Is it polling periodically?
If you want application or platform level tasks, you’re better off scheduling a task on which ever job queue you run. That could also be pg.
That way you can have platform-wide unique tasks, probably better monitoring / tracing, etc.