in reply to Database queue logic

I would have a single process that watches and updates the table which farms records out to worker processes--pre-forking if performance dictates.

How fast do you want to check for new records? Rather than repeatedly querying the table, you might consider an insert trigger (not sure if that could work) or tailing a log file instead.

--Solo

--
You said you wanted to be around when I made a mistake; well, this could be it, sweetheart.