Since I submitted that patch.. I guess I should answer.

The code in vpopmail was first trying to connect to the server for a given 
database. If that was failing, it would try the server only and if that 
succeeded, it was considering that the server was fine but that the DB was 
not created.

Apparently, under some load, it could happen that the first request would 
fail, but the second would be accepted... 

All the patch does is make the code connect to the server first and then use 
the Database. If the first call fails, the delivery fails (temporary failure) 
and the message is delivered later.


> On Fri, 25 Jun 2004 18:17:53 -0700
> Tom Collins <[EMAIL PROTECTED]> wrote:
> > http://vpopmail.sf.net
> >
> > Release Notes:
> >
> > There are significant changes in here for MySQL and Postgres backends.
> >
> > If you've had errors stating "couldn't create table/database because it
> > already exists" with MySQL, you should definitely upgrade.
> Well, I was having such errors with 5.4.3, and I did upgrade. It seems to
> be working fine, now. I noticed that this error occured only with the
> server under heavy load (over 8, 10). Since it is fixed now in 5.4.5, I
> have a question out of curiosity: What was the bug that was causing this
> error?
> Thanks,
> Jean

Reply via email to