Hacker News new | past | comments | ask | show | jobs | submit login

This is awesome and I will take a closer look! One question: We ran into issue with using Postgres as a message queue with messages that need to be toasted/have large payloads (50mb+).

Only fix we could find was using unlogged tables and a full vacuum on a schedule. We aren’t big Postgres experts but since you are I was wondering if you have fixed this issue/this framework works well for large payloads.






Don't put them in the queue. Put the large payload into an object store like s3/gcs and put a reference into the db or queue

Yep - this is also the official recommended method by Hatchet, also sometimes called payload thinning.



Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: