Francesco Capponi

@rascalDan did you end up finding a solution? e.g. adding some configs such as `replica_batch_size = 1000000`

Could you please share a fully runnable SQL and pg_chameleon example to reproduce so we can check on my side as well? I saw your previous description, but to get...

Hi @the4thdoctor, is this case now being handled?

@kagkarlsson thanks for the comment! One of the use cases, is when you have a set of tasks that always have to be run before the others. Let's say you...

In the other post you put it in better words than mine: `Do you require to be able to set priority on instance-level, or would task-level work? I.e., for a...

This can be helpful also in low throughput, long queues situations. Ideally we could have something that is not a workaround, since the queues could possibly be many, and then...

`For adding support for task-priority to the scheduler, wouldn't the best solution be to add the priority field to the database table, and have the query for getDue fetch executions...

`Do you require to be able to set priority on instance-level, or would task-level work? I.e., for a given task, all instances have the same priority` Both are useful. Cardinality...

I'm pretty sure that the index on two fields should work pretty well. Queries on two ranges shouldn't be a problem. Multiple queries are for sure less performant than one...

Sure, in theory the highest cardinality one should always be first in the index, which in this case is execution_time. If you imagine a index execution_time, priority, where priority has...