Cindy, if I'm following this correctly, we'd keep creeping up after each restart until the bug is fixed.

Just a thought -- could we negotiate a price for the occasional restarting (resetting? whatever the term is) of MySQL? That would come in between the $20 and the $200 support level, surely.

(Since I know very little about how much labor is involved or whether the labor/services can be priced accordingly, I just throw this out without knowing if it's a laughable idea or not.)

Cindy, if I'm following this correctly, we'd keep creeping up after each restart until the bug is fixed.

Okay, I wondered, but don't think of that as us creeping up, but rather an effect of the bug in the code. Thank you, aurelia.

I like Theodosia's idea.

As we get closer to Thursday, I still vote for Kristen's proprosal even if this code error gets fixed. Unless the host changes attitude, I'd like more responsive service, and I think that requires larger sums of money.

If this error is (as it seems to be) a MySQL bug, I sort of resent us paying (or having the Buffistas chip in the lion's share towards what amounts to) a 100% increase, just to get a response from our ISP (not Kristen, IH--Kristen sweats blood for us)--especially if all we're asking for is for him to reset the daemon when this bug kicks in.

I realize the bug isn't his fault, but it sounds like it isn't our fault, either. Kristen, have you heard from Steven?

a 100% increase

1000% increase, actually.

I realize the bug isn't his fault, but it sounds like it isn't our fault, either.

It is our fault in the sense that we selected MySQL for our system, which means we would have this problem where ever we were hosted. I can see Steve's point of view. We chose to use the software with the bug in it, and if that choice requires extra attention from the host, then we need to pay for it.

I haven't heard back from Steven. I just poked him a little while ago about it. For all I know, he's on a rooftop somewhere manning a garden hose.

As for the rest, I really don't see the point of having this conversation again. You guys should make whatever decision you feel is best for the community but staying here in this current configuration is not a long term option, unless you're willing to live with the error messages.

It is our fault in the sense that we selected MySQL for our system, which means we would have this problem where ever we were hosted.

No, we'd only have this problem at places that use the MySQL per-user connection limit as a way of limiting server resource use for shared hosting. Not all hosts do it that way.

Netgate just gives you a CPU/memory limit and you get an error from in your browser if an attempt to load a page exceeds the account limits.

Dreamhost has this conuries system, where you don't have a limit but you pay more a a lot extra if you exceed your allocation. At our rate of use we'd be their favorite customer, but that's another issue.

So moving to another shared hosting situation isn't necessarily going to put us in this situation again, but I think the stress for the stompies would be much less with a dedicated server. They wouldn't have to worry that each small change to the Phoenix code might put them in dutch with the host.

They wouldn't have to worry that each small change to the Phoenix code might put them in dutch with the host.

And, that will cost more money, but not necessarily 1000% more.