On 2/4/06, geni geniice@gmail.com wrote:
On 2/4/06, The Cunctator cunctator@gmail.com wrote:
On 2/4/06, geni geniice@gmail.com wrote:
On 2/4/06, The Cunctator cunctator@gmail.com wrote:
I'm not avoiding your points, I don't buy your logic. Yes, guns are an extreme comparison and, I think, a poor analogy. The thought of holding a funeral for the loss of a Wikipedia image is pretty entertaining, though.
How long a database lock do you view as acceptable?
I'm not sure what you're talking about -- you're going to have to help me here..
It is fairly trivial for an admin to trigger a database lock. Depending on what they do exactly it could be quite a long one.
Can you explain what you mean by "database lock"? Or point me to a reference? I'm happy to RTFM.
The Cunctator wrote:
Can you explain what you mean by "database lock"? Or point me to a reference? I'm happy to RTFM.
Basically where an admin does something which means that everything else gets put on hold until the "something" is completed. For example, deleting a page with a large history (such as when Ed Poor deleted AFD).
Chris
On 2/4/06, Chris Jenkinson chris@starglade.org wrote:
Basically where an admin does something which means that everything else gets put on hold until the "something" is completed. For example, deleting a page with a large history (such as when Ed Poor deleted AFD).
[[George W. Bush]] would do.
-- Sam
"Chris Jenkinson" chris@starglade.org wrote in message news:43E50127.4090702@starglade.org...
The Cunctator wrote:
Can you explain what you mean by "database lock"? Or point me to a reference? I'm happy to RTFM.
Basically where an admin does something which means that everything else gets put on hold until the "something" is completed. For example, deleting a page with a large history (such as when Ed Poor deleted AFD).
IIRC this also happened when SnowSpinner "deprecated" {{if}} by replacing the functional (but horrible, don't get the idea I fail to agree with that :-) code with a notice saying that this template had been deprecated and should be replaced.
I recall reports that it took about 15 minutes to recover, but I can't remember whether this was for the DB lock, or for all uses to be replaced. I do know it was surprisingly fast, even for those of us who had been expressing scepticism that any one template could hold the DB to ransom :-)