|
|
|
|
|
by orthoxerox
1150 days ago
|
|
Yes, that's basically what we ended up doing: a queue of tasks in Postgres that a variable number of workers could access via a clever SP that encapsulated all inter-task conflicts and spat out the next task you were allowed to process. |
|
Are there any links that could be helpful to work through the programs and caveats of such a SP?
Part of it for me is creating a table that can store the process in the database to be able to traverse it reasonably.