feature-request: can a Queue has state like 'pause' or 'running'

[elvizlai]

Sometimes, the queue needs state control, especially for consumers/subscribers.
Typically, such states (running, pause) do not affect the producer. However, there could also be special states like "stopped" to manage production and pushing.

Is it possible for us to add this state control?

[ChuckHend]

Something like this should be possible.

One way could be through the use of roles and priveldges. For example, have separate roles created for the consumers and producers. Then control read and write access by changing those priveldges. Something like REVOKE INSERT, UPDATE, DELETE, TRUNCATE ON ALL TABLES IN SCHEMA pgmq FROM pgmq_consumers;. I think would be close to pausing the queue for the consumers. This method wouldn't need any changes to the pgmq project and could be tailored to your specific use case.

There's probably something that could be built into the pgmq project directly too, but I'll need to think about it a bit more.

[v0idpwn]

But why? I understand the need to pause queues if you have a push model, but for a pull model, it doesn't seem necessary.

[elvizlai]

For example: the consumer downstream has something wrong or uncontrolled behavior, need just stop consuming but not all whole application.
Maybe we can check how other MQ did this?

[v0idpwn]

I'm not aware of any pull-based MQ solution that has this feature.