View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005321 | Taler | exchange | public | 2018-04-10 19:35 | 2019-12-20 18:12 |
| Reporter | Florian Dold | Assigned To | Christian Grothoff | 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 | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 0.6 | Fixed in Version | 0.6 | ||
| Summary | 0005321: investigate database problems in wirewatch | ||||
| Description | Right now wirewatch logs some scary warning about failed transactions. Either we don't treat this soft error properly as a soft error, or we do treat is as a soft error and retry, but then we probably shouldn't log a "scary" message with PGRES_FATAL_ERROR. We should also try to figure out why this conflict happened, and if we can do anything to reduce the chance of it happening (i.e. use some index instead of linear scan etc.) | ||||
| Additional Information | Apr 03 20:06:06-888222 pq-13913 INFO Query `reserve_create' failed with result: could not serialize access due to read/write dependencies among transactions/Reason code: Canceled on identification as a pivot, during write./ERROR: could not serialize access due to read/write dependencies among transactions DETAIL: Reason code: Canceled on identification as a pivot, during write. HINT: The transaction might succeed if retried. /PGRES_FATAL_ERROR/ERROR: could not serialize access due to read/write dependencies among transactions DETAIL: Reason code: Canceled on identification as a pivot, during write. HINT: The transaction might succeed if retried. | ||||
| Tags | No tags attached. | ||||
| Went manually over exchange (all tools) and merchant backend fixing all cases where rollback was missing. Merchant: c993c0d..04692ee, exchange: 14908b78155aade720a58c15be502bb317cea540 (harmless). | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2018-04-10 19:35 | Florian Dold | New Issue | |
| 2018-04-10 19:35 | Florian Dold | Status | new => assigned |
| 2018-04-10 19:35 | Florian Dold | Assigned To | => Christian Grothoff |
| 2018-08-18 11:35 | Christian Grothoff | Status | assigned => informing |
| 2018-08-18 11:35 | Christian Grothoff | Resolution | open => fixed |
| 2018-08-18 11:35 | Christian Grothoff | Fixed in Version | => 0.6 |
| 2018-08-18 11:35 | Christian Grothoff | Note Added: 0013221 | |
| 2018-08-18 11:35 | Christian Grothoff | Product Version | => git (master) |
| 2018-08-18 11:35 | Christian Grothoff | Target Version | => 0.6 |
| 2018-08-18 11:35 | Christian Grothoff | Additional Information Updated | |
| 2019-12-20 18:12 | Christian Grothoff | Status | informing => closed |