You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if this is the root cause or a contributing factor, but loadNextIdArchive() does not auto-increment. (klando's pgsql port uses a sequence object here. However, if archiving should fail, it results in an orphaned row.)
The quick fix is to add the IGNORE (discard) keyword to the INSERT.
Ideally, Multiple concurrent archiving processes should be avoidable...
The text was updated successfully, but these errors were encountered:
Multiple concurrent archiving could be avoidable by a database-level lock, or by a simple file based lock.
However, agreed with you that Piwik should not fail while this lock system is not implemented. agreed on the quick fix using IGNORE (I believe it won't have side effects).
Symptom:
http://forum.piwik.org/index.php?showtopic=1513
I don't know if this is the root cause or a contributing factor, but loadNextIdArchive() does not auto-increment. (klando's pgsql port uses a sequence object here. However, if archiving should fail, it results in an orphaned row.)
The quick fix is to add the IGNORE (discard) keyword to the INSERT.
Ideally, Multiple concurrent archiving processes should be avoidable...
The text was updated successfully, but these errors were encountered: