Perhaps a real fix would be to add a UNIQUE(task_id, aggregate_share_id) constraint to the aggregate_share_jobs table.
Originally posted by @jcjones in #4766 (comment)
DAP-19 (4.6.4. Obtaining Aggregate Shares) says:
A Helper aggregate share is identified by a server-selected
identifier, unique within the scope of the task, assigned during
resource creation (Section 3.2).
So we should enforce that.
Perhaps a real fix would be to add a
UNIQUE(task_id, aggregate_share_id)constraint to theaggregate_share_jobstable.Originally posted by @jcjones in #4766 (comment)
DAP-19 (4.6.4. Obtaining Aggregate Shares) says:
So we should enforce that.