Interest in a PostgreSQL result backend

[jtcho]

Hi,

I see that there is Celery/Redis backend support out of the box – but unfortunately I've been using PostgreSQL as a result backend for my own project until I can migrate to Redis.

I plan to write a lightweight Postgres backend wrapper based off of the Celery one – https://github.com/celery/celery/blob/master/celery/backends/database/models.py . Since the interface provided by gocelery is simple (GetResult/SetResult), I imagine it would be pretty straightforward.

Do you / folks think there would be interest if I were to open a PR with it here, even as a proof of concept?

[ftntming]

That would be awesome!

[jtcho]

@ftntming This ended up being more tricky than I anticipated, because Celery pickles all task results in the DB backend. I tried using a couple golang pickle deserializers with minimal success. Instead, I ended up just writing a thin wrapper around the python celery that shells out and reads stderr/stdout.

[ftntming]

@ftntming This ended up being more tricky than I anticipated, because Celery pickles all task results in the DB backend. I tried using a couple golang pickle deserializers with minimal success. Instead, I ended up just writing a thin wrapper around the python celery that shells out and reads stderr/stdout.

No worries man. I found that too. I realized that, implementations of Celery clients in golang/nodejs all lack the enhanced features of Celery task features, e.g. Chained, so I'm now more inclined to stick with Python Celery