On Wednesday, June 27, 2012 5:02:26 PM UTC-7, ptressel wrote: > > This won't solve your installation / setup issue, but I wonder if it would > help with the overrun and timeout problems... Instead of scheduling a > periodic task, what about having the task reschedule itself? When it's > done with the queue, schedule itself for later. Remove the time limit so > it can take whatever time it needs to finish the queue. Or maybe launch a > process on startup outside of the scheduler -- when it exhausts the queue, > have it sleep and either wake periodically to check the queue, or have it > waked when something is inserted. >
I don't see why we'd do this instead of just setting stop_time=infinity and repeats=0. > Is the transaction processing issue you encountered with PostgreSQL > preventing you from setting up your queue as a real producer consumer > queue, where you could have multiple workers? > No, I only want one worker. The scheduler itself works great as a producer/consumer queue. I may have mislead you with the title of this thread—I'm trying to set up a general repeating background process, not a task queue in particular. Processing a task queue was just one use of the repeating background process function.
