[wp-hackers] postmeta databasing issues

Aaron Brazell emmensetech at gmail.com
Tue May 30 22:13:34 GMT 2006

On 5/30/06, David Chait <davebytes at comcast.net> wrote:
> I should note that I posted about this error many moons ago, as it spawned
> multiple discussion threads about what it meant.  Always seemed to be the
> _pingme stuff, no other problems.
> -d

I vaguely remember that. I couldn't find it in the archives though.

>This is a MySQL server error, not related to WordPress. Usually this is
>caused by:
>* MySQL dying
>* wait_timeout too low
>* Custom DB code closing the connection

The only thing that I see in that list is the wait_timeout and that was
already at 40 seconds. I just bumped that to 50 and republished an entry.
Same error. I suppose I'll try 60, then 70 then 80... But this is not the
answer.  Why is this query taking up so much time and energy from the
server? The server has been optimized... over-optimized... continually
monitored and refactored for demand.  It's not custom code as it is
happening on every single blog, every single time a publish/edit is done and
some of these blogs are off the shelf, no custom code.

More information about the wp-hackers mailing list