On 5/23/11 10:00 AM, Tim Starling wrote:
On 23/05/11 23:37, William Allen Simpson wrote:
The only solution I've found is to log-in insecure, check the history, and then log out. Then, the history is up-to-date for non-logged-in.
Why do we cache history?
We don't. Maybe you're seeing replication lag rather than caching. That would explain why the secure site magically fixes itself when you do an unrelated task that takes a few minutes.
Aha, replication lag would explain it! Since I'm only doing things on off hours, how long should replication lag be these days?