3 ms·
Oban looks fantastic! PG is fantastic for a small-medium job queue IMHO. pg_notify with elixirs postgrex is fantastic. We're currently using ecto_job which wor
by thejosh 7y ago
Oban looks fantastic! PG is fantastic for a small-medium job queue IMHO. pg_notify with elixirs postgrex is fantastic.
We're currently using ecto_job which works really well for us, so we have no reason to switch. Plus we like it's in different tables.
- pselbert 7y agoIt seems like PG has been pigeonholed as only suitable for “small-medium” size queues, but without numbers to define what “small-medium” means. A few million jobs an hour is entirely reasonable for PG based on anectdata (and I’ve load tested up to 54 million jobs an hour). PG is an amazing tool that can handle more than most people think (or at least more than I thought).
- heavenlyblue 7y agoWhat about VACUUM? Did they add something to PostgreSQL to lower space consumption?
- pselbert 7y agoThere has been some progress on that front. For index size there is a new rebuild command in PG12 which works concurrently. There is also pluggable storage now, which enables much more efficient row deletion. I can’t find a link to the new storage format, but here is the announcement for 12 https://www.postgresql.org/about/news/1943/ https://www.postgresql.org/about/news/1943/