Erm... it still does it. Your message was logged in for Thur Mar 10, but after logging in and returning to the board index it's now down as Wed Mar 9. Are you sure that message approval has anything to do with it?
It's not a serious problem so far, and probably not going to do anything nasty. But you know how bugs are. If you don't know the exact cause, you don't know how bad it really is. It's not going to wipe out anyone's credit history, but I'd hate to see the site crash.
I'm remembering the time I asked a colleague at work, a sys admin, to show me how to monitor disk space usage on a DEC mini system I was using. He said, "Oh, sure, it's easy." A few quick keystrokes brought up a display that caused him to gasp as if he'd swallowed a wasp. "NINETY EIGHT PERCENT FULL!!! WHAT?????"
Turns out that he had a job that ran every four hours, which kept a log file. In the command line parameters for the log file, he had accidentally typed an 'a' instead of an 'r'. So, every time it ran, it didn't (R)eplace the old log file, it (A)ppended a revised copy. Therefore, the log file was at least doubling in size every time the job ran. If I hadn't asked that innocent little question at just that time, the job would have run again while we were all home enjoying dinner. Hard crash city.
The job seemed
to be running OK.
Lac lactis in primoris (milk in first).