View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010063 | Taler | exchange | public | 2025-06-03 13:19 | 2025-06-21 22:24 |
| Reporter | Christian Grothoff | Assigned To | Resolution deadline | ||
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | low | Severity | tweak | Reproducibility | always |
| Status | implementing | Resolution | open | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | 1.0 stretch goals | ||||
| Target Version | post-2.0 | ||||
| Summary | 0010063: taler-exchange-sanctioncheck always iterates over all pending records | ||||
| Description | The SELECT has no LIMIT, and so the transaction could be rather BIG (and possibly fail with serialization errors because of that). So for good performance (and reliability), we should limit the number of records processed in one transaction. | ||||
| Tags | performance | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-06-03 13:19 | Christian Grothoff | New Issue | |
| 2025-06-03 13:19 | Christian Grothoff | Tag Attached: performance | |
| 2025-06-03 13:19 | Christian Grothoff | Status | new => implementing |
| 2025-06-21 22:24 | Christian Grothoff | Severity | feature => tweak |