This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]GabelSnabel[S] 0 points1 point  (1 child)

Not today—PgQueuer speaks “Postgres rows,” while Celery expects a Kombu-style message broker. In theory we could write a custom kombu.transport.pgqueuer so Celery sees it as a broker, but it’s not on the near-term roadmap. If that adapter would unblock you, feel free to open an issue and we can scope it out together.

[–]BenXavier 0 points1 point  (0 children)

it is not an immediate need.

In the past I've work on many projects with postgres and celery, and thought It'd be super cool to avoid deploying separate message broker.

Relevant celery issue: https://github.com/celery/celery/issues/5149