| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
score, also checking squid access.log for squark annotations
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
missing
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
a new one with the same name.
Symptom was running out of shared memory in postgres because there were thousands of savepoints.
|
| |
|
|
|
|
| |
Stangely enough, I saw a case where the logme resulted in an error, and the whole transaction was lost.
|
| |
|
|
|
|
| |
error and continue
|
| |
|
| |
|
|
|
|
| |
or short reason in log.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Better error reporting for the line that caused the error.
Continue to do the purging even if import fails.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|