Ok, I stupidly submitted a bug report about mysql_pconnect being broken and I'd like to change my bug report to a constructive design gripe. =)

If you have to have one mysql connection per web server thread or child why even bother using mysql_pconnect?  For a server with 10+ children, you are talking about a lot of memory waste.  It would make much more sense to use one connection for all children.  I imagine that the way that the apache server works and the way threading is in the mysql client libraries would keep this from being possible, but please, please consider adding this to the mysql_pconnect documentation.  The blurb about this in the faq has not always been there and those of us who've read the faq before, in particular the persistant connection part, don't always think about seeing if that one section has been updated.

And also...  Although this is the intended operation of mysql_pconnect, as evident in the amount of bug reports about it, it's not the way that people would expect or hope that it would work.  It's useless to me because I have to set my query buffer memory high due to the amount of data I move back and forth through queries.

Please take this as constructive feedback.. PHP is still THE best web server module on earth.